dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0288

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 10.2.7 / 10.2.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 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.

In the news

Third-party coverage
Trending covered by 3 outlets this week · latest 4w ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple buffer overflow vulnerabilities in the User-ID Terminal Server Agent (TSA) component of Palo Alto Networks PAN-OS allow an unauthenticated remote attacker with network access to send specially crafted network traffic, potentially causing denial of service or arbitrary code execution.

MitigationRestrict User-ID Terminal Server Agent connectivity to trusted internal IP addresses only, following the vendor's recommended best practice deployment guidelines.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pan OsOperating system
Affected:>= 10.2.0, < 10.2.7>= 10.2.8, < 10.2.10>= 10.2.11, < 10.2.13>= 10.2.14, < 10.2.16= 10.2.7= 10.2.10= 10.2.13= 10.2.16= 10.2.17= 10.2.18>= 11.1.0, < 11.1.4>= 11.1.8, < 11.1.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine PAN-OS version
    Run 'show system info' on the firewall CLI or check Device > Setup > Operations in the web UI to retrieve the installed PAN-OS version number.
    Affected if The installed version falls within any of the affected ranges: 10.2.0-10.2.6, 10.2.8-10.2.9, 10.2.11-10.2.12, 10.2.14-10.2.15, 10.2.16-10.2.18, 11.1.0-11.1.3, or 11.1.8-11.1.9.
  2. Verify User-ID feature is enabled
    Run 'show user-id-collector status' or 'show user-id service' on the CLI to confirm the User-ID service is active.
    Affected if User-ID is enabled and running.
  3. Confirm Terminal Server Agent is configured
    Run 'show user-id tms status' or 'show user-id agent terminal-server' on the CLI to check if the TSA (Terminal Server Agent) is provisioned.
    Affected if The Terminal Server Agent is configured and active.
  4. Check TSA network binding and exposure
    Run 'show user-id tms server' or review the TSA listener configuration to determine which IP addresses and ports the agent is bound to.
    Affected if The TSA is listening on interfaces accessible from untrusted or external networks, not restricted to trusted internal IPs only.

You are affected if your PAN-OS version is within the vulnerable ranges AND the User-ID Terminal Server Agent is enabled and exposed to network paths reachable by untrusted actors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.2.7 / 10.2.10 / 10.2.13 or later
Fixed in 10.2.710.2.1010.2.13
Interim mitigation

Restrict User-ID Terminal Server Agent connectivity to trusted internal IP addresses only, following the vendor's recommended best practice deployment guidelines.

Recommended fix High confidence

PAN-OS 10.2.16 or later (any 10.2.x release >= 10.2.16)

  1. 1. Identify your current PAN-OS version from the Device > Dashboard > General Information page in the web interface.
  2. 2. Based on the affected version ranges, upgrade to PAN-OS version 10.2.16 or later (the next unreleased version in the 10.2.x branch that is not listed as vulnerable).
  3. 3. Download the recommended PAN-OS release from the Palo Alto Networks Customer Support Portal.
  4. 4. Upload the upgrade file to the firewall or Panorama and install the update.
  5. 5. After upgrade, verify the User-ID Terminal Server Agent (TSA) is functioning correctly under Device > User Identification > Terminal Server Agent.
  6. 6. Alternatively or additionally, restrict TSA connectivity to trusted internal IP addresses only by configuring the TSA listen-addresses to bind to specific trusted internal interfaces/IPs as per the best practice deployment guidelines referenced in the advisory.
Caveat Standard PAN-OS upgrade precautions apply - review release notes for behavioral changes and ensure compatibility with connected devices before upgrading production firewalls.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pan Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0288 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data