dbcve.org
Prisma Access AgentApplication · Paloaltonetworks

CVE-2026-0247

HIGH · 7.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 26.2.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Multiple authorization bypass vulnerabilities in the Endpoint DLP component of Prisma Access Agent® allow a local attacker to bypass authentication controls and execute privileged operations.

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 confidence

Multiple authorization bypass vulnerabilities exist in the Endpoint DLP component of Prisma Access Agent that allow a local attacker to bypass authentication controls and execute privileged operations. This is a local privilege escalation issue in the Data Loss Prevention module.

MitigationApply vendor patches for Prisma Access Agent when available; until then, limit physical and logical access to systems running Endpoint DLP and monitor for suspicious privileged operations.

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
Affected:< 26.2.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Prisma Access Agent installation
    Check for Prisma Access Agent in installed programs (Windows: Add/Remove Programs, Programs and Features; macOS: Applications folder, Launchpad; Linux: dpkg -l, rpm -qa, or looking in /Applications)
    Affected if Prisma Access Agent is not found on the system - not affected. If found, continue to version check.
  2. Determine installed version of Prisma Access Agent
    Open Prisma Access Agent application, go to Help > About, or check the version through system utilities (Windows: wmic product get name,version; macOS: defaults read /Applications/Prisma\ Access\ Agent.app/Contents/Info CFBundleVersion; Linux: check the agent binary or configuration files)
    Affected if Version is present and less than 26.2.1 - the system is potentially affected by the vulnerability.
  3. Confirm Endpoint DLP component status
    Access Prisma Access Agent settings or configuration panel; look for Endpoint DLP or Data Loss Prevention module status. On Windows, check the Prisma Access Agent service in Services.msc for DLP-related components; on Linux check running processes for dlp-related services
    Affected if Endpoint DLP component is enabled or running - the specific attack surface for this CVE exists.
  4. Check for recent authentication or privilege events
    Review Windows Event Viewer Security logs, macOS unified logs, or Linux audit logs (/var/log/audit/audit.log) for unexpected authentication events or privilege escalation attempts around the Prisma Access Agent service account
    Affected if Unexpected authentication events or privilege escalation activity is observed - may indicate exploitation attempts.

The environment is affected if Prisma Access Agent with Endpoint DLP enabled is installed at a version prior to 26.2.1, as the authorization bypass vulnerabilities exist specifically in the Endpoint DLP component of those versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 26.2.1 or later
Fixed in 26.2.1
Interim mitigation

Apply vendor patches for Prisma Access Agent when available; until then, limit physical and logical access to systems running Endpoint DLP and monitor for suspicious privileged operations.

Recommended fix High confidence

26.2.1

  1. 1. Verify current Prisma Access Agent version by checking the agent's About or version information in the system tray or application settings
  2. 2. Download Prisma Access Agent version 26.2.1 or later from the Palo Alto Networks support portal at support.paloaltonetworks.com
  3. 3. If auto-update is enabled, the agent may automatically update; otherwise, manually run the installer for the new version
  4. 4. During installation, accept any license agreements and allow the upgrade to complete
  5. 5. After upgrade, verify the new version is 26.2.1 or higher in the agent's About section
  6. 6. Confirm Endpoint DLP functionality is operational post-upgrade

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,140
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0247 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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