# CVE-2026-0288: PAN-OS: Buffer Overflow Vulnerabilities in User-ID Terminal Server Agent

> Unauthenticated attackers can cause denial of service or execute arbitrary code via buffer overflows in the User-ID Terminal Server Agent.

- **Severity:** High 7.2 (`CVSS: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/AU:N/R:U/V:D/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-rgmm-652r-crf4

## What is CVE-2026-0288?

CVE-2026-0288 is a high-severity memory corruption vulnerability in Paloaltonetworks Pan-Os, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-0288?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2026-0288?

No fix has been published for CVE-2026-0288 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0288 being exploited?

There is no known exploitation of CVE-2026-0288 in the wild and no public exploit code.

## Other vulnerabilities in Paloaltonetworks Pan-Os

- [CVE-2024-3400](https://insights.sbomify.com/CVE-2024-3400/): Palo Alto Networks PAN-OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2020-2021](https://insights.sbomify.com/CVE-2020-2021/): Palo Alto Networks PAN-OS Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2017-15944](https://insights.sbomify.com/CVE-2017-15944/): Palo Alto Networks PAN-OS Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2026-0300](https://insights.sbomify.com/CVE-2026-0300/): Palo Alto Networks PAN-OS Out-of-bounds Write (critical 9.3, exploited in the wild)
- [CVE-2024-0012](https://insights.sbomify.com/CVE-2024-0012/): Palo Alto Networks PAN-OS Management Interface Authentication Bypass (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0288 and fix it if it is affected.

What it is: CVE-2026-0288 is a high-severity memory corruption vulnerability in Paloaltonetworks Pan-Os, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0288 in the wild and no public exploit code.

Affected product: Paloaltonetworks Pan-Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0288/ (Markdown: https://insights.sbomify.com/CVE-2026-0288/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0288
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0288
- OSV: https://osv.dev/vulnerability/CVE-2026-0288

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0288/
Summaries are generated and may contain mistakes; the official description above is the record.