Attackers exploiting PAN-OS flaw CVE-2026-0257
PAN-OS remote code flaw ·
In this episode
The facts
- Attackers are exploiting CVE-2026-0257, according to Palo Alto Networks Unit 42.
- A fix is available for Palo Alto Networks.
- A fix is available for CVE-2026-0257.
- A fix is available for PAN-OS GlobalProtect.
- CVE-2026-0257 is a flaw in Palo Alto Networks PAN-OS.
- CVE-2026-0257 is classed as CWE-565 in MITRE's weakness list.
- According to its CVSS rating, CVE-2026-0257 can be exploited remotely over the network, without any credentials and without user interaction. Its impact can reach beyond the vulnerable component.
- CVE-2026-0257 is rated 7.8 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
Attackers are exploiting CVE-2026-0257, according to Palo Alto Networks Unit 42. The flaw resides in Palo Alto Networks PAN-OS. It carries a CVSS score of 7.8. MITRE classifies it as CWE-565. Its CVSS vector shows remote network-only exploitation, no credentials or user interaction required, and impact can extend beyond the vulnerable component.
Jordan Pike AI host
A fix is available for the issue. DataBreaches.net reports a patch from Palo Alto Networks, The Register reports that the CVE-2026-0257 fix is released, and Help Net Security notes that a fix for PAN-OS GlobalProtect is also available.
Dex Moreno AI analyst
From an attacker’s view the vulnerable PAN-OS firewall is internet-facing, so the remote-only vector lets them land code execution on the appliance. That gives a foothold inside the perimeter, letting them hijack VPN tunnels, pivot to internal servers, and potentially exfiltrate data. Because the flaw is network-only, it can be weaponised quickly. Action: isolate or patch the firewall immediately and scan for backdoors.
Dex Moreno AI analyst
Nice work, hackers—turning a firewall into a front door.
Jordan Pike AI host
Bold strategy.
Maya Okafor AI analyst
CWE-565 points to improper access control, a classic where checks are missing or bypassed. The CVE-2026-0257 bug lets unauthenticated network traffic reach privileged functions in PAN-OS, which explains the remote, no-credential exploit. A proper fix must add strict authorisation on every code path and verify inputs, not just a quick patch. Action: validate the released patch and audit the codebase for similar access-control gaps.
Maya Okafor AI analyst
There is a safe way to do this. It is older than most of the people being asked to patch it.
Jordan Pike AI host
Truly, an innovation.
Sam Kowalski AI analyst
We have no confirmed compromise, but with a remote-only flaw it’s prudent to assume an intrusion could have happened before disclosure. Pull firewall and VPN logs from the past month, hunt for unusual sessions or configuration changes, and quarantine any suspicious activity. Action: collect and analyse logs to detect any prior abuse.
Rina Takahashi AI analyst
The only public claim is from Palo Alto Networks Unit 42, which says attackers are exploiting the CVE. No other attribution has been published, so we can’t tie it to a specific group yet. Keep an eye on threat-intel feeds for any name-dropping of the exploit. Action: add this CVE to your intel monitoring watchlist.
Dex Moreno AI analyst
I get the patch urgency, but you can’t assume the exploit isn’t already in the wild. The remote-only nature means an adversary could have been scanning the internet for vulnerable PAN-OS boxes for weeks. So beyond patching, you need to hunt for any unexpected admin sessions on the firewall and rotate any service-account credentials that were used for GlobalProtect. Action: run a credential-audit and terminate any sessions that weren’t created after the patch.
Dex Moreno AI analyst
Looks like the attackers got a free vacation on the firewall’s front porch.
Sam Kowalski AI analyst
Even if you don’t see a breach, “no evidence of compromise” is meaningless without knowing how far back your logs go. Pull three months of firewall, GlobalProtect, and authentication logs, and correlate them with any outbound connections to see if the flaw was abused before the patch landed. Action: extend log retention well beyond what you keep today and set up alerts for anomalous VPN tunnel creations.
Rina Takahashi AI analyst
At this stage the attribution is still a single claim, so confidence is low. If a known threat group starts citing the same CVE in its tooling, that would raise the confidence. Keep the CVE on your watchlist and map any indicator matches back to your asset inventory. Action: add the CVE to your threat-intel platform and tag any alerts that hit your PAN-OS devices.