Firewall policy bypass via incorrect IPv6 sizing
Published Jul 9, 2026 · Updated Jul 9, 2026
Incorrect buffer-size calculation in Palo Alto Networks PAN-OS and Prisma Access allows remote attackers to bypass IPv6 firewall policy. The dataplane's IPv6 packet-processing path calculates a buffer size incorrectly, causing policy enforcement to pass traffic that a configured rule should block. Exposure requires IPv6 on at least one firewall interface; successful traffic can reach protected services without altering or interrupting the firewall itself.
Summary
What happened
Incorrect buffer-size calculation in Palo Alto Networks PAN-OS and Prisma Access allows remote attackers to bypass IPv6 firewall policy. The dataplane's IPv6 packet-processing path calculates a buffer size incorrectly, causing policy enforcement to pass traffic that a configured rule should block. Exposure requires IPv6 on at least one firewall interface; successful traffic can reach protected services without altering or interrupting the firewall itself.
The record
- CVE
- CVE-2026-0280
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- Palo Alto Networks
- Product
- PAN-OS
- Classifications
- CWE-131, CAPEC-153, T1562.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.2.0 <10.2.18-h8 changes=[{"at":"10.2.18-h8","status":"unaffected"},{"at":"10.2.16-h9","status":"unaffected"},{"at":"10.2.13-h23","status":"unaffected"},{"at":"10.2.10-h39","status":"unaffected"},{"at":"10.2.7-h36","status":"unaffected"}]
- Affected versionversion=11.1.0 <11.1.16 changes=[{"at":"11.1.16","status":"unaffected"},{"at":"11.1.13-h9","status":"unaffected"},{"at":"11.1.10-h30","status":"unaffected"},{"at":"11.1.7-h8","status":"unaffected"},{"at":"11.1.6-h35","status":"unaffected"},{"at":"11.1.4-h35","status":"unaffected"}]
- Affected versionversion=11.2.0 <11.2.13 changes=[{"at":"11.2.13","status":"unaffected"},{"at":"11.2.10-h11","status":"unaffected"},{"at":"11.2.7-h18","status":"unaffected"},{"at":"11.2.4-h20","status":"unaffected"}]
- Affected versionversion=12.1.0 <12.1.8 changes=[{"at":"12.1.8","status":"unaffected"},{"at":"12.1.7-h2","status":"unaffected"},{"at":"12.1.4-h8","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo