Cyber Resilience

CVE-2026-0288

Memory Safety in Paloaltonetworks Pan-Os 10.2.0 – 10.2.7

Published
08 July 2026
Modified
10 July 2026
Patch / advisory
CVSS Score v4 7.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/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:N/R:U/V:D/RE:M/U:Red
EPSS Score 0.0084 54th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-0288 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Paloaltonetworks Pan-Os. Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

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

EU & UK References

Vulnerability Data

Multiple buffer overflow vulnerabilities in the User-ID Terminal Server Agent (TSA) component of Palo Alto Networks PAN-OS software allow an unauthenticated attacker with network access to cause a denial of service (DoS) condition or potentially execute arbitrary code by sending…

more

specially crafted network traffic. The security risk posed by this issue is minimized when the User-ID Terminal Server Agent connectivity is restricted to only trusted internal IP addresses according to our recommended best practice deployment guidelines https://docs.paloaltonetworks.com/ngfw/help/10-2/user-identification/device-user-identification-terminal-services-agents#:~:text=To%20minimize%20security%20risk%2C%20restrict%20TS%20Agent%20connectivity%20to%20trusted%20internal%20IP%20addresses%20only. . Panorama is 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?

Buffer overflow in the User-ID Terminal Server Agent (TSA) exposed to network traffic directly enables remote code execution or denial of service against a publicly reachable service, mapping to T1190 (Exploit Public-Facing Application).

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

CVEs Like This One

CVE-2024-9468Same product: Paloaltonetworks Pan-Os
CVE-2025-0282Same product class: VPN / SSL gateway
CVE-2024-21762Same product class: VPN / SSL gateway
CVE-2023-22640Same product class: VPN / SSL gateway
CVE-2024-37377Same product class: VPN / SSL gateway
CVE-2024-52963Same product class: VPN / SSL gateway
CVE-2023-22639Same product class: VPN / SSL gateway
CVE-2018-13383Same product class: VPN / SSL gateway
CVE-2023-42789Same product class: VPN / SSL gateway
CVE-2024-12248Shared CWE-787

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)
  • SC-7 Boundary Protection
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
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

Boundary protection can enforce network-level restrictions that limit User-ID TSA connectivity to only trusted internal addresses, directly blocking unauthenticated external attackers from reaching the vulnerable component.

prevent

Access enforcement can implement the policy that only explicitly authorized internal hosts may communicate with the TSA service, preventing the crafted traffic that triggers the buffer overflows.

prevent

Information flow enforcement can be configured to restrict or drop traffic flows to the TSA from any source outside the defined trusted internal address set, mitigating the attack vector.

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-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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.

detects

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

prevents

Secure development life cycle mandates practices that prevent out-of-bounds writes.

prevents

Application security requirements can specify bounds-checking and safe memory handling.

prevents

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References