Cyber Resilience

CVE-2026-0280

Paloaltonetworks Pan-Os 10.2.0 – 10.2.7

Published
09 July 2026
Modified
13 July 2026
Patch / advisory
CVSS Score v4 1.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:D/RE:M/U:Amber
EPSS Score 0.0018 8th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-0280 is a low-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Paloaltonetworks Pan-Os. Its CVSS base score is 1.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An IPv6 packet processing vulnerability in the dataplane of Palo Alto Networks PAN-OS® software enables an unauthenticated attacker to bypass firewall security policy enforcement, allowing network traffic that should be blocked to reach protected services. Cloud NGFW and Panorama are…

more

not impacted by this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

The vulnerability allows unauthenticated attackers to bypass firewall security policy enforcement via IPv6 packet processing, directly enabling exploitation of a public-facing network security device (T1190: Exploit Public-Facing Application).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-0284Same product: Paloaltonetworks Pan-Os
CVE-2026-0285Same product: Paloaltonetworks Pan-Os
CVE-2026-0288Same product: Paloaltonetworks Pan-Os
CVE-2026-0273Same product: Paloaltonetworks Pan-Os
CVE-2025-0111Same product: Paloaltonetworks Pan-Os
CVE-2026-0263Same product: Paloaltonetworks Pan-Os
CVE-2025-0108Same product: Paloaltonetworks Pan-Os
CVE-2024-9474Same product: Paloaltonetworks Pan-Os
CVE-2024-5913Same product: Paloaltonetworks Pan-Os
CVE-2025-0114Same product: Paloaltonetworks Pan-Os

Affected Assets

paloaltonetworks
pan-os
10.2.10, 10.2.13, 10.2.16, 10.2.17, 10.2.18 · 10.2.0 — 10.2.7 · 10.2.8 — 10.2.10 · 10.2.11 — 10.2.13

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-4 Information Flow Enforcement
  • AC-3 Access Enforcement
  • SC-7 Boundary Protection
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces information flow policies on network packets, preventing the IPv6 dataplane bypass that allows traffic to reach protected services.

prevent

Enforces firewall security policy decisions on all traffic, blocking the unauthenticated IPv6 policy bypass described in the CVE.

prevent

Implements boundary protection mechanisms such as firewalls that the vulnerability circumvents for IPv6 traffic.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent buffer-size miscalculations via coding standards, reviews, and testing, while fixing this single weakness only partially fulfills the broader control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Secure coding standards directly require correct buffer-size calculations.

detects

Security testing can detect buffer-size errors before release.

prevents

Secure development lifecycle mandates size-checking practices that reduce buffer-size miscalculations.

prevents

Application security requirements can specify buffer-size validation rules.

prevents

Secure architecture principles include safe memory-allocation guidelines.

References