Disclosure up front: I work at Zscaler, which competes with Palo Alto Networks. So this is a competitor writing about a competitor's advisory. Every fact below comes from Palo Alto's advisory as reported publicly, linked at the end.
I'll also say this before anything else: this is not a five-alarm fire. It's a medium-severity bug that requires an authenticated administrator, and Palo Alto says it isn't aware of any malicious exploitation. I'm writing it up because of where it lives, not because of how loud it is.
What We Know
Per Palo Alto's advisory for CVE-2026-0330, published November 11, as reported by Cyber Security News and Cyberpress:
- The bug: code injection (CWE-94) in PAN-OS on Panorama, the central management server for Palo Alto firewalls.
- Who can exploit it: an authenticated administrator with network access to Panorama. Not unauthenticated, no user interaction.
- Severity: Palo Alto rates it medium. CVSS 4.0 base score 8.6, threat-adjusted 6.1.
- Affected: Panorama on PAN-OS 12.2, 12.1, 11.2, 11.1 and 10.2.
- Not affected: standalone PAN-OS firewalls, Cloud NGFW and Prisma Access.
- Exploitation: none known, per Palo Alto. Cyber Security News specifically notes that exploitation of the separate CVE-2026-0322 is not evidence that this one is being used.
- Fixed in: 12.2.4-h2, 12.1.10-h4, 11.2.16-h2, 11.1.16-h5 and 10.2.18-h14 on the latest lines, with hotfixes for older maintenance releases. Pick the one for your branch; hotfix numbers aren't interchangeable.
- Workaround: none that fully fixes it. Palo Alto recommends restricting management access to trusted internal IPs, ideally through a dedicated jump box.
Palo Alto hasn't published the vulnerable endpoint or how the injection works, and I'm not going to guess at it.
Credit Where It's Due
This is a vendor finding and fixing a bug before anyone's known to be using it, with a clear advisory, fixed versions for every supported branch, a CVSS-BT score that's honest about the current threat, and credit to the external researcher (Daniel Voce). That's how this is supposed to work.
Why "Requires Admin" Isn't the End of the Story
"Requires admin" is reassuring right up until an admin account gets phished, or an earlier bug hands out admin. Attackers chain things. A post-auth code execution bug on the box that pushes policy to every firewall in the company is a very useful second step.
That's the architecture point, and it applies to every vendor, Zscaler included: whatever controls the policy for your whole network is the highest-value target you own. Centralized management is great for operations, and it also concentrates blast radius. The less reachable it is, and the fewer accounts can touch it, the less any single bug matters.
What To Do If You Run Panorama
- Upgrade to the fixed hotfix for your branch. Check the advisory for your exact maintenance release.
- Lock down management access to trusted internal IPs, through a dedicated jump box. If your Panorama is reachable from the internet, fix that first.
- Audit Panorama admin accounts. Remove stale ones, enforce MFA, and use role-based access so not every admin is a superuser.
- Threat Prevention subscribers: Cyberpress reports Threat IDs 510045 and 510048 give limited coverage, but only with SSL decryption enabled. That's a backstop, not the fix.
- Watch the advisory for any change in exploitation status.
Bottom Line
A medium, admin-only, unexploited bug is the best kind to patch: before it matters. Panorama sits above every firewall it manages, so update it, wall it off, and keep the admin list short.
Sources: Palo Alto Networks advisory CVE-2026-0330, Cyber Security News, Cyberpress