Prisma Access AgentApplication · Paloaltonetworks
CVE-2026-0248
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 · uneditedAn improper certificate validation vulnerability in the Prisma Access Agent® for Android and Chrome OS enables an attacker to perform a man-in-the-middle (MitM) attack to intercept VPN traffic. By presenting a certificate for any domain issued by a trusted Certificate Authority, the attacker can capture sensitive device information. The Prisma Access Agent on macOS, Windows, Linux and iOS are not affected.
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 confidenceThe Prisma Access Agent for Android and Chrome OS contains an improper certificate validation vulnerability that fails to properly verify the authenticity of SSL/TLS certificates. This allows a man-in-the-middle attacker to present a certificate issued by any trusted Certificate Authority and successfully intercept VPN traffic, capturing sensitive device information.
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
Prisma Access AgentApplication
< 26.2.1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Prisma Access Agent version on AndroidOpen the Google Play Store app, search for Prisma Access Agent, tap on it, and view the version number displayed under the app name. Alternatively, go to Settings > Apps > Prisma Access Agent to see the version.Affected if The displayed version number is lower than 26.2.1
-
Check installed Prisma Access Agent version on Chrome OSOpen the Google Play Store on Chrome OS, locate the Prisma Access Agent app, and view the version information in the app listing details.Affected if The displayed version number is lower than 26.2.1
-
Check version via app package information on AndroidUse ADB to run: adb shell pm list packages | grep prisma, then adb shell dumpsys package <package_name> | grep versionNameAffected if The versionName field shows a version lower than 26.2.1
-
Compare version to affected rangeDocument the exact version number found and compare it numerically to 26.2.1Affected if The installed version is any release prior to 26.2.1 (for example, 26.2.0, 26.1.x, 26.0.x, or earlier)
You are affected if the installed version of Prisma Access Agent on your Android device or Chrome OS is lower than 26.2.1, as the certificate validation flaw exists in all prior versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped26.2.1
Apply vendor patches from Palo Alto Networks for the Prisma Access Agent on Android and Chrome OS; until patches are available, users should avoid untrusted networks and organizations may consider network-level SSL inspection or additional controls.
26.2.1
- Open the Google Play Store (Android) or Chrome Web Store (Chrome OS) on the device
- Search for "Prisma Access Agent" or access it through your organization's software distribution method
- Locate Prisma Access Agent in the app store or software catalog
- Update the application to the latest available version
- Alternatively, if deployed via enterprise mobile device management (MDM), push the update 26.2.1 or later through your MDM console
- After update completes, verify the version by checking the app settings or about section to confirm version 26.2.1 or higher is installed
- Restart the VPN connection if currently active to ensure the patched client is fully operational
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prisma Access Agent
Scoped from the published advisory
- Consultation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0248 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0248 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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