Skip to content
VulniPulse
Medium6.3Vendor: LowPalo Alto Networks

Medium [CVE-2026-0280] PAN-OS: IPv6 Firewall Policy Bypass

This medium-severity Palo Alto Networks advisory covers CVE-2026-0280 affecting PAN-OS, Prisma Access.

CVE-2026-0280 Published Jul 8, 2026
Affected products & platforms
Palo Alto NetworksPAN-OSFirewallPrisma AccessPAN-OS / Panorama
Open vendor advisory

Android app · Google Play

Monitor future Palo Alto Networks CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

CVE-2026-0280 PAN-OS: IPv6 Firewall Policy Bypass

Affected products named by the advisory: Prisma Access.

Affected versions
  • PAN-OS < 12.1.8
  • PAN-OS < 11.2.13
  • PAN-OS < 11.1.16
  • PAN-OS < 10.2.18-h8
  • Prisma Access < 11.2.7-h18
  • Prisma Access < 10.2.10-h39

Official advisory · high-confidence parse· fetched 8 days ago·verify at source

Fixed versions
  • PAN-OS >= 12.1.8
  • PAN-OS >= 12.1.7-h2
  • PAN-OS >= 12.1.4-h8
  • PAN-OS >= 11.2.13
  • PAN-OS >= 11.2.10-h11
  • PAN-OS >= 11.2.7-h18
  • PAN-OS >= 11.2.4-h20
  • PAN-OS >= 11.1.16
  • PAN-OS >= 11.1.13-h9
  • PAN-OS >= 11.1.10-h30
  • PAN-OS >= 11.1.7-h8
  • PAN-OS >= 11.1.6-h35
  • PAN-OS >= 11.1.4-h35
  • PAN-OS >= 10.2.18-h8
  • PAN-OS >= 10.2.16-h9
  • PAN-OS >= 10.2.13-h23
  • PAN-OS >= 10.2.10-h39
  • PAN-OS >= 10.2.7-h36
  • Prisma Access >= 11.2.7-h18
  • Prisma Access >= 10.2.10-h39

Official advisory · high-confidence parse· fetched 8 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • VersionMinor VersionSuggested SolutionCloud NGFWNo action needed.
  • PAN-OS 12.1 12.1.5 through 12.1.7-h* Upgrade to 12.1.7-h2 or 12.1.8 or later. 12.1.2 through 12.1.4-h* Upgrade to 12.1.4-h8 or 12.1.8 or later.
Temporary workarounds
  • The only way to completely address this vulnerability is to upgrade to a fixed version.
  • However, if operationally feasible for your environment, risk can be mitigated by enabling the default "Non SYN TCP Reject" setting via the following command:
  • set deviceconfig setting session tcp-reject-non-syn yes

Official advisory · high-confidence parse· fetched 8 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.