CVE-2026-0288 remediation guide
Palo Alto Networks Cloud NGFW, PAN-OS, Prisma Access
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-identifi...
Identify the affected asset
Confirm whether Palo Alto Networks Cloud NGFW, PAN-OS, Prisma Access is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: 12.1.0, 11.2.0, 11.1.0, 10.2.0, >= 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, >= 11.1.11 < 11.1.13, >= 11.1.14 < 11.1.16, 11.1.4, 11.1.5. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 10.2.7, 10.2.10, 10.2.13, 10.2.16, 11.1.4, 11.1.10, 11.1.13, 11.1.16, 11.2.4, 11.2.7, 11.2.10, 11.2.13, 12.1.4, 12.1.7. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.