Prisma Access AgentApplication · Paloaltonetworks
CVE-2026-0245
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 · uneditedMultiple 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.
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 · moderate confidenceMultiple information disclosure vulnerabilities in Prisma Access Agent allow a local authenticated user to access sensitive configuration data and plaintext credentials stored on the affected system. The vulnerabilities affect Windows and macOS versions of the Prisma Access Agent client. CVE details indicate local privilege escalation or improper access control leading to credential exposure.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Prisma Access Agent installationCheck if Prisma Access Agent client is installed on the system. On Windows, look in Program Files or Program Files (x86) for a Palo Alto Networks folder. On macOS, check /Applications for Prisma Access Agent.app.Affected if Prisma Access Agent is found installed on the system
-
Identify installed Prisma Access Agent versionOn Windows, check the version via the application Properties or in Add/Remove Programs. On macOS, right-click the application and select Get Info to view the version. Alternatively, check the executable file properties.Affected if Installed version is lower than 26.2.1 (e.g., 26.2.0, 26.1.x, or earlier)
-
Locate Prisma Access Agent configuration filesSearch for configuration directories or files associated with Prisma Access Agent. Common locations include user AppData folders on Windows or Application Support directories on macOS. Look for config, settings, or credential-related files.Affected if Configuration files exist and contain sensitive data such as plaintext credentials or API keys
-
Inspect configuration file permissionsCheck file system permissions on configuration directories and files. Verify if low-privileged users can read sensitive configuration files that should be restricted to administrator or system accounts.Affected if Non-admin users have read access to files containing credentials or sensitive configuration data
-
Search for plaintext credentials in config storageOpen and inspect configuration files or credential storage locations used by Prisma Access Agent. Look for patterns indicating stored passwords, API tokens, or other secrets in plaintext rather than encrypted format.Affected if Plaintext credentials or sensitive configuration data are found in accessible config files
User is affected if Prisma Access Agent version is below 26.2.1 and configuration files containing plaintext credentials or sensitive data are readable by local authenticated users.
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-supplied patches or updates for Prisma Access Agent when available. Until then, restrict local access to systems running the agent, minimize the number of privileged local accounts, and monitor for unauthorized access to configuration files or credential stores.
Prisma Access Agent 26.2.1 or later
- 1. Identify the current version of Prisma Access Agent installed on the affected Windows system
- 2. Download Prisma Access Agent version 26.2.1 or later from the official Palo Alto Networks support portal
- 3. Apply the upgrade following Palo Alto Networks standard upgrade procedures for Prisma Access Agent
- 4. Verify the installed version is 26.2.1 or higher after upgrade completion
- 5. Confirm the vulnerability is remediated by testing that local users can no longer access sensitive configuration data and credentials
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
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0245 — 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-0245 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