Palo Alto Networks PAN-OS: attackers can run their own code
OFFICIAL NAME: Palo Alto Networks PAN-OS Code Injection Vulnerability
WHAT IT IS · VPN, FIREWALL OR GATEWAYIt sits at the edge of your network and faces the internet, so attackers can reach it directly.
DO THIS FIRSTIf you have it, patch it today. If you cannot, block access to it from the internet until you can. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY Palo Alto Networks PAN-OS contains a code injection vulnerability that could allow an authenticated attacker with network access to execute arbitrary code with root privileges on the firewall.
WHY THIS VERDICT Attacks are confirmed. The vulnerability is 27 days old, so many systems are likely still unpatched. It affects a product that faces the internet or gives remote access.
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. The product faces the internet or gives remote access. 4 products are affected.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- PROOF OF CONCEPT CLAIMED
How far has it climbed?
01 TALK
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESCVE-2026-0322 discussed publicly (CIRCL sighting). CVE-2026-0322 discussed publicly (CIRCL sighting).
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESCISA Vulnrichment marks CVE-2026-0322 as actively exploited. Palo Alto Networks PAN-OS contains a code injection vulnerability that could allow an authenticated attacker with network access to execute arbitrary code with root privileges on the firewall.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICCLAIMED
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. The deadline CISA set for US federal agencies, Oct 17, 2026, has passed. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run Palo Alto Networks PAN-OS? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- Attack activity. OCT 13, 2026Palo Alto Networks PAN-OS Code Injection Vulnerability
- Attack activity. OCT 14, 2026CISA Vulnrichment marks CVE-2026-0322 as actively exploited
- OCT 14, 20261 public GitHub repository claims a proof of concept for CVE-2026-0322
- OCT 15, 2026Palo Alto Networks security advisory (AV26-1041) - Update 1
- OCT 25, 2026CVE-2026-0322 discussed publicly (CIRCL sighting) (2 reports, latest NOV 5)
SOURCES
- [1] CIRCL Vulnerability-Lookup sightings: CVE-2026-0322 discussed publicly (CIRCL sighting), NOV 5
- [2] Canadian Centre for Cyber Security: Palo Alto Networks security advisory (AV26-1041) - Update 1, OCT 15
- [3] PoC-in-GitHub: 1 public GitHub repository claims a proof of concept for CVE-2026-0322, OCT 14
- [4] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-0322 as actively exploited, OCT 14
- [5] CISA Known Exploited Vulnerabilities: Palo Alto Networks PAN-OS Code Injection Vulnerability, OCT 13
- [6] CIRCL Vulnerability-Lookup sightings: 1 more reports