Palo Alto Networks PAN-OS Code Injection
CVE-2026-0322 is a high-severity improper control of generation of code vulnerability in Cloud NGFW from Palo Alto Networks, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. CISA added it to the Known Exploited Vulnerabilities catalogue on October 14, 2026, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update PAN-OS to 12.2.4 or 12.1.10-h2 or 11.2.16 or 11.1.16-h3, whichever matches your release line, or a later version.
- CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Read the advisory on security.paloaltonetworks.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Palo Alto Networks | Cloud NGFW | Not specified in the record | Not stated |
| Palo Alto Networks | PAN-OS | 12.2.0 up to, but not including, 12.2.4; 12.1.0 up to, but not including, 12.1.10-h2; 11.2.0 up to, but not including, 11.2.16; 11.1.0 up to, but not including, 11.1.16-h3; 10.2.0 up to, but not including, 10.2.18-h12 | 12.2.4, 12.1.10-h2, 11.2.16, 11.1.16-h3, 10.2.18-h12 |
| Palo Alto Networks | Prisma Access | Not specified in the record | Not stated |
| Siemens | RUGGEDCOM APE1808 | all versions | Not stated |
| Siemens | Ruggedcom Ape1808 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.6 | High | CNA (paloaltonetworks.com) |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
A remote code execution (RCE) vulnerability in the management interface of Palo Alto Networks PAN-OS® software enables an authenticated attacker with network access to execute arbitrary code with root privileges on the firewall. The security risk posed by this issue is minimized by restricting access to the management interface to only trusted internal IP addresses according to our recommended best practice deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 . This issue is applicable to PAN-OS software on PA-Series and VM-Series firewalls and on Panorama (virtual and M-Series). Cloud NGFW and Prisma® Access are not impacted by this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cert-portal.siemens.com/productcert/html/ssa-104023.htmlThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322US Government Resource
Our coverage
Other vulnerabilities in Cloud NGFW
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
- 7.2 High severity
- 9.9 Critical severity
- 7.2 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 8.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.2 High severity
Spotted an error? Tell us.