Palo Alto PAN-OS zero-day CVE-2026-0322 exploited, patch now

five months after the CVE-2026-0300 buffer overflow, Palo Alto Networks is once again dealing with an exploited flaw in its firewalls. On October 14, 2026, the Santa Clara-based company published fixes for CVE-2026-0322 , a code injection bug in the PAN-OS management interface that lets an already authenticated user run code with root privileges. In its official advisory the company describes the exploitation as "very limited". CISA has since added the flaw to its Known Exploited Vulnerabilities catalog, with a remediation deadline of October 17.

Palo Alto Networks is an American cybersecurity company best known for its firewalls, the appliances that filter traffic between an organization's internal network and the internet. PAN-OS is the operating system they run on, while Panorama is the console used to manage many firewalls from a single place. These boxes sit on the perimeter of companies and public bodies of every size. That is why root-level code execution on one of them matters well beyond the security crowd.

Cyber Security News picked up the story with a post that sums up the essentials.

Hackers Exploit Palo Alto PAN-OS 0-day Flaw to Gain Root Code Execution on Firewalls Hackers are exploiting a high-severity flaw in Palo Alto Networks PAN-OS that allows authenticated attackers to run code with root privileges on affected firewalls. — Cyber Security News (@The_Cyber_News) October 15, 2026

Hackers Exploit Palo Alto PAN-OS 0-day Flaw to Gain Root Code Execution on Firewalls Hackers are exploiting a high-severity flaw in Palo Alto Networks PAN-OS that allows authenticated attackers to run code with root privileges on affected firewalls.

What CVE-2026-0322 allows an attacker to do

The advisory rates the flaw high severity, with a CVSS 4.0 score of 8.6 and a CWE-94 weakness, meaning code injection (the system ends up executing outside text as a command). Exploiting it takes two things, valid credentials with high privileges and network reachability of the management interface. Palo Alto says no special configuration is needed, so there is no option to switch off to get out of the way.

The outcome is arbitrary code execution as root, the highest level of control over the system. At that level an attacker can rewrite any filtering rule, read what passes through the appliance and leave persistent software behind. An 8.6 should be read, in practice, as a high-urgency item and not a routine notice. The score drops only slightly, to 8.5, if management access is limited to a jump box (a dedicated intermediate server, the only place from which the firewall can be reached).

Which products and versions are affected

The flaw hits PAN-OS on PA-Series and VM-Series firewalls and on Panorama, both virtual and M-Series. Cloud NGFW and Prisma Access are not affected and need no action. Versions that are already out of support must be moved to a supported branch, because no fix is coming for them.

Anyone on the 11.2 branch should check their build closely, because the fix listed as final, 11.2.16, was due out on October 15 itself. What counts is the installed build and not the branch. The complete, up-to-date list stays with the advisory.

How to defend yourself if you cannot patch today

Palo Alto states that there is no known workaround . There are only partial mitigations, to apply while waiting for the patch and not in place of it.

Limit access to the management interface to trusted internal IP addresses, removing direct internet exposure if it is still there.

With a Threat Prevention subscription, enable the signatures with Threat ID 510046 and 510047 (content from 9159-10287 onward), which cover the traffic only in part and require SSL decryption.

Route management traffic through a data plane port, replace the management certificate, and enable decryption and threat prevention on inbound traffic.

The company warns that variants of the attack may exist that current signatures do not detect, so the mitigations buy time without closing the problem. For after-the-fact checks, Palo Alto has published three IP addresses tied to the attacks, 66.42.72[.]14, 208.83.239[.]114 and 149.248.47[.]234, to hunt for in the management interface access logs.

Why a flaw that needs credentials still hurts

An 8.6 instead of a 9 or higher hands out a bit of false comfort, because the attacker must already hold an administrative account. In practice, though, firewall credentials are not a reliable lock (they end up in infostealers, they get reused elsewhere), and a management interface reachable from the wrong network turns a stolen account into root on the appliance that is supposed to protect everything else.

The pattern shows up in recent days too. On October 14 the patch landed for the exploited Ivanti Connect Secure zero-day , on October 5 CISA sounded the alarm over a critical RCE in MikroTik RouterOS and on October 3 it was the turn of FortiMail with a 9.8 zero-day . Perimeter appliances remain the favorite target, always on, seeing all the traffic, rarely watched by an antivirus.

It is not Palo Alto's first time this year. In May it was the turn of CVE-2026-0300 , an already exploited buffer overflow in the User-ID authentication portal. According to SecurityWeek , the CISA catalog now counts 16 vulnerabilities in Palo Alto products, three of them added in 2026.

What is still unknown

No source has attributed the attacks to a specific group. BleepingComputer notes, for its part, that the questions most useful to anyone running a firewall remain unanswered. It is unclear when exploitation began, whether the affected appliances were compromised in depth, and whether anyone used them as a bridgehead into internal networks.

The discovery was internal, the work of Suraj Siddharudh, a product security researcher at Palo Alto Networks. The same day the company published a dozen other advisories covering PAN-OS, GlobalProtect and Prisma Cloud, all of medium or low severity, so it is worth doing one single update round instead of chasing patches one at a time. October 14 also brought fixes for five NGINX vulnerabilities , worth cross-checking against the inventory of exposed servers. A similar picture emerged in October's Patch Tuesday , where the three zero-days were the tip of a very long list.

What to do by tonight

Check the build in use on every PA-Series, VM-Series and Panorama, including appliances forgotten in labs.

Install the fixed build for your branch, or plan the move to a supported branch.

Verify which networks can reach the management interface and shut it to anything that is not a trusted host.

the management logs for the three IP addresses published by Palo Alto.

Rotate administrative credentials if even a single log line looks suspicious.

Frequently asked questions (FAQ)

1. Is my firewall at risk if the management interface is not on the internet?

Less exposed, but not safe. The attacker must reach the management interface over the network and hold valid credentials, so an interface closed to the internet shrinks the attack surface a lot, while anyone already inside the internal network or holding a stolen account can still exploit it. That is why the patch remains the right answer.

2. Why did CISA set the deadline at October 17?

Because the flaw is in the Known Exploited Vulnerabilities catalog. For US federal civilian agencies, a listing in the catalog counts as an obligation to mitigate by the stated date, October 17 in this case. For everyone else it is a priority signal, not a mandate.

3. Are Cloud NGFW and Prisma Access affected?

No. Palo Alto states that both are unaffected and require no action from customers.

4. Are the Threat Prevention signatures enough instead of the patch?

No, they cover only part of the cases. The signatures with Threat ID 510046 and 510047 require SSL decryption. Palo Alto itself warns that unrecognized variants may exist. They serve to buy time while the update is being planned.

The most uncomfortable part of this story is the pairing of a reassuring score with exploitation already under way. Anyone running Palo Alto firewalls should treat CVE-2026-0322 as a hole to close this week, starting with appliances whose management interface can be reached from networks nobody has reviewed in years. Fixes exist for almost every branch, while for 11.2 one was arriving today. An 8.6 that reassures more than it should.

The flaw gives root on the firewall to anyone who already has an administrative account and can reach the management interface. It is already being used in attacks. If you cannot patch today, restrict management to trusted internal hosts and the logs for the three IPs published by Palo Alto.