CVE
PAN-OS: Authenticated Remote Code Execution (RCE) in Panorama
- Exploited
- No known exploitation
- Fix
- Fixed in 12.2.4-h2, 12.1.7-h12, 11.2.13-h5, 11.1.13-h17, 10.2.16-h13
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 12.2.4-h2, 12.1.7-h12, 11.2.13-h5, 11.1.13-h17, 10.2.16-h13.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A remote code execution flaw in Palo Alto Networks PAN-OS software on Panorama lets an authenticated administrator with network access run arbitrary code with root privileges. The attacker must already have administrator login credentials and reaches the flaw over the network.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A remote code execution (RCE) vulnerability in Palo Alto Networks PAN-OS® software on Panorama enables an authenticated administrator with network access to execute arbitrary code with root privileges.
The security risk posed by this issue is significantly 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 .
Cloud NGFW, Prisma® Access, and standalone PAN-OS firewalls are not affected by this vulnerability.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach14/20Affects Palo Alto PAN-OS (an enterprise product or network appliance)
- Severity6.1/10CVSS 6.1
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 12.2.4-h2, 12.1.7-h12, 11.2.13-h5, 11.1.13-h17, 10.2.16-h13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-0330 (PAN-OS: Authenticated Remote Code Execution (RCE) in Panorama), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-0330 (entry last updated 2026-11-11):
Affected:
- Palo Alto Networks Cloud NGFW: version range not reported
- Palo Alto Networks PAN-OS: from 12.2.0, fixed in 12.2.4-h2; from 12.1.0, fixed in 12.1.7-h12; from 11.2.0, fixed in 11.2.13-h5; from 11.1.0, fixed in 11.1.13-h17; from 10.2.0, fixed in 10.2.16-h13
- Palo Alto Networks Prisma Access: version range not reported
Fixed versions: 12.2.4-h2, 12.1.7-h12, 11.2.13-h5, 11.1.13-h17, 10.2.16-h13.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-0330 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-0330 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://security.paloaltonetworks.com/CVE-2026-0330
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-0330
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-0330"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Palo Alto Networks Cloud NGFW
Version range not reported
- Palo Alto Networks PAN-OS
From 12.2.0 · fixed in 12.2.4-h2; From 12.1.0 · fixed in 12.1.7-h12; From 11.2.0 · fixed in 11.2.13-h5; From 11.1.0 · fixed in 11.1.13-h17; From 10.2.0 · fixed in 10.2.16-h13
- Palo Alto Networks Prisma Access
Version range not reported
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-0330
Is CVE-2026-0330 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-0330?
PAN-OS: from 12.2.0 before 12.2.4-h2; from 12.1.0 before 12.1.7-h12; from 11.2.0 before 11.2.13-h5; from 11.1.0 before 11.1.13-h17; from 10.2.0 before 10.2.16-h13.Source: cve.now feed data
How do I fix CVE-2026-0330?
Upgrade to a fixed version: 12.2.4-h2, 12.1.7-h12, 11.2.13-h5, 11.1.13-h17, 10.2.16-h13.Source: cve.now feed data