# CVE-2026-0322: Palo Alto Networks PAN-OS Code Injection

> Authenticated attackers can execute arbitrary code with root privileges on PAN-OS firewalls via the management interface.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:N/R:U/V:D/RE:M/U:Red`)
- **Exploited in the wild:** Yes, since 14 Oct 2026 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-9fh3-97mp-7wmv

## What is CVE-2026-0322?

CVE-2026-0322 is a high-severity code injection vulnerability in Paloaltonetworks Pan-Os, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-0322?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2026-0322?

No fix has been published for CVE-2026-0322 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Oct 2026.

## Is CVE-2026-0322 being exploited?

Yes. Attackers have exploited CVE-2026-0322 in the wild since at least 14 Oct 2026.

Public exploit code:

- CVE-2026-0322 (github_poc): https://github.com/Ife-ella/CVE-vulnerability

## Other vulnerabilities in Paloaltonetworks Pan-Os

- [CVE-2024-3400](https://insights.sbomify.com/CVE-2024-3400/): Palo Alto Networks PAN-OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2020-2021](https://insights.sbomify.com/CVE-2020-2021/): Palo Alto Networks PAN-OS Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2017-15944](https://insights.sbomify.com/CVE-2017-15944/): Palo Alto Networks PAN-OS Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2026-0300](https://insights.sbomify.com/CVE-2026-0300/): Palo Alto Networks PAN-OS Out-of-bounds Write (critical 9.3, exploited in the wild)
- [CVE-2024-0012](https://insights.sbomify.com/CVE-2024-0012/): Palo Alto Networks PAN-OS Management Interface Authentication Bypass (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0322 and fix it if it is affected.

What it is: CVE-2026-0322 is a high-severity code injection vulnerability in Paloaltonetworks Pan-Os, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-0322 in the wild since at least 14 Oct 2026.

Affected product: Paloaltonetworks Pan-Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0322/ (Markdown: https://insights.sbomify.com/CVE-2026-0322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0322
- OSV: https://osv.dev/vulnerability/CVE-2026-0322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0322/
Summaries are generated and may contain mistakes; the official description above is the record.