Prisma Access AgentApplication · Paloaltonetworks
CVE-2026-0277
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 iOS enables an attacker to perform a man-in-the-middle (MitM) attack to intercept VPN traffic. The Prisma Access Agent on Windows, macOS, Linux, Android and ChromeOS 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 iOS contains an improper certificate validation vulnerability that allows man-in-the-middle attackers to intercept VPN traffic. The iOS client fails to properly validate the VPN server's SSL/TLS certificate, enabling attackers to impersonate the VPN server and capture sensitive traffic.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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.
-
Verify Prisma Access Agent for iOS is installedCheck the iOS device for the Prisma Access Agent app in Settings > General > VPN & Device Management, or locate the app icon on the device home screenAffected if The Prisma Access Agent app is present on the iOS device
-
Identify the installed version numberOpen the Prisma Access Agent app, navigate to Settings > About, or check the version listed in the iOS App Store if installed via MDMAffected if The displayed version number is less than 26.2.1 (for example, 26.2.0, 26.1.x, or earlier)
-
Confirm VPN configuration is activeGo to Settings > VPN on the iOS device and verify a Prisma Access VPN configuration exists and shows as Connected or has a configuration profile installedAffected if A Prisma Access VPN configuration is enabled and actively used
-
Check network exposureDetermine whether the device has connected or will connect to untrusted networks (public WiFi, hotspots) while using the VPNAffected if The device is used on untrusted networks while the VPN connection is active or being established
A user is affected if Prisma Access Agent for iOS with a version lower than 26.2.1 is installed and has an active VPN configuration that could be exposed to untrusted networks.
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
Update Prisma Access Agent for iOS to the patched version provided by Palo Alto Networks. Until a patch is available, avoid connecting to the VPN over untrusted networks.
26.2.1
- Upgrade Prisma Access Agent for iOS to version 26.2.1 or later
- Verify the upgrade was successful by checking the application version in the iOS device settings or app store
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prisma Access Agent
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0277 — 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-0277 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