Reported exploitation of Palo Alto Cloud NGFW flaw
CISA KEV alert ·
In this episode
The facts
- Attackers are exploiting CVE-2026-0322, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- CVE-2026-0322 is a flaw in Palo Alto Networks Cloud NGFW.
- CISA has given US federal agencies until October 17, 2026 to fix CVE-2026-0322.
- CVE-2026-0322 is classed as code injection (CWE-94).
- According to its CVSS rating, CVE-2026-0322 can be exploited remotely over the network, only with administrative privileges and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
- CVE-2026-0322 is rated 8.6 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CISA reports attackers are exploiting CVE-2026-0322 and have added it to the Known Exploited Vulnerabilities catalog. The flaw resides in Palo Alto Networks Cloud NGFW.
Jordan Pike AI host
The vulnerability is classified as code injection (CWE-94) and carries an 8.6 CVSS score. According to the CVSS vector it can be triggered remotely over the network, requires administrative privileges, needs no user interaction, and a successful exploit fully compromises confidentiality, integrity and availability.
Jordan Pike AI host
CISA has given US federal agencies until October 17, 2026 to remediate CVE-2026-0322.
Dex Moreno AI analyst
From an attacker’s viewpoint, the cloud NGFW sits at the network edge, exposing a management interface that is reachable from the internet. With admin credentials the code-injection bug lets them execute arbitrary code on the appliance, effectively taking control of the firewall itself. That foothold grants visibility into all inbound and outbound traffic and the ability to pivot to any downstream services that trust the firewall for segmentation. My recommendation: isolate the affected firewalls, block external admin access, and begin a forced password reset while you work on remediation.
Dex Moreno AI analyst
Looks like they turned a firewall into a front door—nice touch.
Jordan Pike AI host
One sentence.
Maya Okafor AI analyst
The bug falls under the code-injection class, where unchecked input is fed to an interpreter or compiler. In this case the NGFW likely builds configuration commands from user-supplied data without proper sanitisation, leading to CWE-94. Because exploitation requires admin rights and no user interaction, the attack surface is limited to privileged accounts, but the impact is total system takeover. A complete fix means validating or rejecting any dynamic code paths and hardening the management API. Apply the vendor’s patch as soon as it’s released and audit all admin accounts for unexpected commands.
Maya Okafor AI analyst
Code injection? More like a code invitation to the party.
Jordan Pike AI host
Bold.
Sam Kowalski AI analyst
For incident responders, the first step is to verify whether any NGFW instances have shown signs of code execution—look for unusual process trees, new admin sessions, or outbound connections to unknown hosts. Pull logs from the management plane, the data plane, and any integrated logging service, and correlate timestamps with the CISA advisory. Even without evidence of compromise, assume the window may be larger than reported. Start a hunt for anomalous admin activity on all Cloud NGFWs and preserve logs for at least ninety days.
Rina Takahashi AI analyst
CISA’s attribution is limited to the vulnerability itself; no specific threat group has been named. However, the KEV listing suggests that active exploit kits are already in the wild, which aligns with historically opportunistic actors who target cloud firewalls for lateral movement. Keep an eye on threat-intel feeds for any indicators of compromise tied to this CVE-2026-0322. Add CVE-2026-0322 to your threat-intel watchlist and alert SOC when exploit traffic is detected.
Dex Moreno AI analyst
Given that this vulnerability is now in the KEV catalog and the asset is internet-facing, I’d treat it as an emergency—patch or isolate within seventy-two hours regardless of any other considerations.
Maya Okafor AI analyst
Patching without a full root-cause analysis can be a band-aid; we should first verify the vendor’s fix addresses the underlying code-injection path and then schedule a coordinated rollout, not a rushed scramble.
Jordan Pike AI host
So for your board: prioritize isolation and credential rotation today, plan for the official patch before the October 17 deadline, and have your SOC hunting for signs of abuse now.