Palo Alto PAN-OS Vulnerability Can Allow Code Execution Through Malicious Network Traffic

Palo Alto Networks has disclosed and patched a PAN-OS vulnerability that can allow an unauthenticated attacker to cause a denial-of-service condition or potentially execute arbitrary code by sending specially crafted network traffic.

The flaw is tracked as CVE-2026-0288 and affects the User-ID Terminal Server Agent component in certain PAN-OS and Prisma Access versions. The official Palo Alto Networks advisory gives it the vendor’s highest urgency rating and says exploitation requires network access to the affected TSA IP and port.

Palo Alto Networks says it is not aware of malicious exploitation at this time. However, exposed deployments should treat the issue as urgent because the attack does not require authentication or user interaction.

What CVE-2026-0288 Affects

CVE-2026-0288 covers multiple buffer overflow vulnerabilities in the User-ID Terminal Server Agent, also known as TSA. The component helps PAN-OS map users to sessions in terminal server environments.

The NVD entry for CVE-2026-0288 describes the issue as a network-reachable flaw that can lead to denial of service or potential arbitrary code execution through crafted traffic.

Only PAN-OS devices with at least one Terminal Server Agent entry configured are affected. Administrators can check this under Device, User Identification, Terminal Server Agents.

Item	Details
CVE	CVE-2026-0288
Product area	PAN-OS User-ID Terminal Server Agent
Weakness type	Out-of-bounds write
Attack vector	Network
User interaction	None
Exploit status	No known malicious exploitation reported by Palo Alto Networks

Why Exposed TSA Configurations Face the Highest Risk

The risk depends heavily on where the Terminal Server Agent is reachable from. Palo Alto Networks says the risk is highest when TSA IP and port access is available from the internet or another untrusted network.

The vendor’s Terminal Server Agent guidance recommends restricting TSA connectivity to trusted internal IP addresses only. That control significantly reduces exposure, even before patching finishes.

Prisma Access has a lower severity rating in this case because exploitation requires an authenticated user and external network access to the TSA IP and port is restricted.

• Highest risk: TSA reachable from the internet or untrusted networks.
• Lower risk: TSA restricted to trusted internal IP addresses.
• Prisma Access risk: medium, due to authentication and restricted access conditions.
• Panorama: not affected by this vulnerability.
• Cloud NGFW on AWS and Azure: not affected, unless Palo Alto Networks contacts the customer directly for Azure.

Affected PAN-OS and Prisma Access Versions

The vulnerability spans several PAN-OS branches. Palo Alto Networks has released fixes across supported versions, while older unsupported versions should be upgraded to a supported fixed release.

NHS England’s cyber alert also lists the affected release ranges and advises organizations to review the vendor advisory and apply the relevant patches as soon as possible. The NHS cyber alert summarizes the issue as a security update for PAN-OS that can prevent denial of service or arbitrary code execution.

Administrators should confirm the exact branch and hotfix line in their environment before upgrading, since fixed versions vary by PAN-OS release train.

Product branch	Affected versions	Fixed versions
PAN-OS 12.1	Before 12.1.4-h8, 12.1.7-h2, or 12.1.8	12.1.4-h8, 12.1.7-h2, 12.1.8 or later
PAN-OS 11.2	Before 11.2.4-h20, 11.2.7-h18, 11.2.10-h12, or 11.2.13	11.2.4-h20, 11.2.7-h18, 11.2.10-h12, 11.2.13 or later
PAN-OS 11.1	Before 11.1.4-h35, 11.1.6-h35, 11.1.7-h8, 11.1.10-h30, 11.1.13-h9, or 11.1.16	Matching fixed hotfix branch or 11.1.16 or later
PAN-OS 10.2	Before 10.2.7-h36, 10.2.10-h39, 10.2.13-h23, 10.2.16-h9, or 10.2.18-h8	Matching fixed hotfix branch or later
Prisma Access 11.2.0	Before 11.2.7-h18	11.2.7-h18 or later
Prisma Access 10.2.0	Before 10.2.10-h39	10.2.10-h39 or later

How the Attack Could Work

The vulnerability comes from buffer overflow issues in the TSA component. A buffer overflow occurs when software writes more data than a memory buffer can safely hold.

MITRE classifies the underlying weakness as CWE-787 out-of-bounds write. In network-facing services, this type of bug can crash the affected process or, in some cases, give attackers a path to execute code.

For CVE-2026-0288, the attacker must have network access to the Terminal Server Agent IP and port. That makes segmentation, firewall policy, and trusted-source restrictions important parts of the defense.

Condition	Security impact
TSA not configured	The device is not exposed to this issue
TSA restricted to trusted internal IPs	Risk drops because attackers need internal network access
TSA reachable from untrusted networks	Risk rises sharply because the attack is network-based and unauthenticated
Unpatched supported PAN-OS branch	Upgrade to the relevant fixed release or hotfix

What Palo Alto Networks Recommends

Palo Alto Networks recommends upgrading affected PAN-OS versions to the fixed releases listed in its advisory. Prisma Access customers will receive upgrades during scheduled maintenance, while customers who need earlier upgrades can contact support for an on-demand upgrade window.

The CVE-2026-0288 advisory also recommends restricting User-ID Terminal Server Agent connectivity to trusted internal IP addresses. This mitigation follows Palo Alto Networks’ best-practice deployment guidance.

Organizations should not rely on the absence of known exploitation as a reason to delay. Network-based vulnerabilities in security appliances often attract rapid attention after public disclosure.

1. Check whether any Terminal Server Agent entries are configured.
2. Identify PAN-OS and Prisma Access versions across the environment.
3. Upgrade affected devices to the relevant fixed version.
4. Restrict TSA access to trusted internal IP addresses only.
5. Confirm that TSA is not reachable from the internet or untrusted networks.
6. Monitor logs for unusual traffic to TSA IPs and ports.

Why Panorama and Cloud NGFW Are Different

Palo Alto Networks says Panorama is not impacted by CVE-2026-0288. Cloud NGFW on AWS and Azure is also listed as unaffected, with the Azure note indicating customers should act only if Palo Alto Networks contacts them.

This distinction matters because PAN-OS deployments vary widely. Some organizations run physical appliances, some use virtual firewalls, and others rely on Prisma Access or Cloud NGFW services.

The National Vulnerability Database currently marks the CVE as awaiting enrichment, but it already mirrors the vendor description and identifies the weakness as out-of-bounds write.

What Security Teams Should Do Now

Security teams should first determine whether the vulnerable configuration exists. If no Terminal Server Agent entry exists, the advisory says the device is not affected by this issue.

If TSA is configured, teams should treat external exposure as the critical triage question. The Palo Alto Networks configuration guidance makes clear that TSA connectivity should stay limited to trusted internal IP addresses.

After exposure review, teams should patch according to branch, validate the upgrade, and keep evidence for compliance or incident-response records. They should also verify that unsupported PAN-OS versions have an upgrade path to a supported fixed version.

• Use asset inventory to find PAN-OS devices with TSA configured.
• Check perimeter rules and NAT rules for TSA exposure.
• Review management and security logs for unexpected TSA traffic.
• Patch exposed systems first, then internally restricted systems.
• Document fixed versions and configuration changes.

Why This Patch Should Be Prioritized

CVE-2026-0288 combines several risk factors that make fast remediation important: network reachability, low attack complexity, no authentication requirement for affected PAN-OS exposure, and possible arbitrary code execution.

Even when exploitation only results in denial of service, the affected product category raises the impact. Firewalls and security gateways sit in sensitive parts of the network, so outages or compromise can disrupt protection, visibility, and access control.

The NHS England Digital alert echoes the vendor guidance and encourages affected organizations to apply relevant patches. The CWE-787 classification also reinforces why memory corruption issues in network-facing components deserve quick attention.

FAQ