⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 4.3

How to Fix CVE-2026-0245: Information Disclosure in Prisma Access Agent

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 4.3 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected0 < 26.2.1
Fixed inAll
Type (CWE)CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

What is CVE-2026-0245?

CVE-2026-0245 is an information disclosure flaw in Prisma Access Agent. The product returns sensitive data to a caller who should not have access, including credentials, session tokens, or configuration. Disclosure often feeds a follow-up attack chain. Vendor description: Multiple information disclosure vulnerabilities in Prisma Access Agent® allow a local user to access sensitive configuration data and credentials. The Prisma Access Agent on Linux, ChromeOS, Android, and iOS are not affected.

Why this CVE matters

Information disclosure flaws are dangerous because they make the next attack easier. Sensitive configuration, session material, or credentials leaked from one endpoint frequently power the follow-on attack that actually takes over the system.

For deployments of Prisma Access Agent that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On PAN-OS, run show system info | match sw-version from the CLI, or read the Dashboard widget in the GUI.

How to fix CVE-2026-0245

  1. Read the vendor advisory in full: https://security.paloaltonetworks.com/CVE-2026-0245
  2. Upgrade Prisma Access Agent to All or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Apply the Android security bulletin update


# Vendor advisory: https://security.paloaltonetworks.com/CVE-2026-0245
# Confirm the device's current Android security patch level
adb shell getprop ro.build.version.security_patch

# Patch level must be on or after 26.2.1.
# Install the OTA from Settings -> System -> System update, or sideload
# the factory image referenced in the advisory.
adb reboot bootloader
fastboot -w update image-<device>-<build>.zip


# Confirm Android Enterprise managed devices have the security patch (Intune example)
Connect-MgGraph -Scopes Device.Read.All
Get-MgDeviceManagementManagedDevice -Filter "operatingSystem eq 'Android'" |
  Select-Object DeviceName, OSVersion, AndroidSecurityPatchLevel

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://security.paloaltonetworks.com/CVE-2026-0245
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2026-0245 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-0245 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-0245?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Prisma Access Agent run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*