Prisma Access AgentApplication · Paloaltonetworks
CVE-2026-0278
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 protection mechanism failures in the Prisma Access Agent Data Loss Prevention (DLP) component for Windows allow a local user to bypass DLP policy enforcement controls. The Prisma Access Agent on macOS is 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 confidenceThe Prisma Access Agent DLP component for Windows contains multiple protection mechanism failures that allow a local authenticated user to bypass DLP policy enforcement controls. An attacker with local access to a Windows endpoint running the Prisma Access Agent could circumvent data loss prevention policies designed to monitor and block sensitive data transfers.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Prisma Access Agent is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Prisma Access Agent' in the installed programs listAffected if Prisma Access Agent does not appear in the installed programs list - the product is not present and therefore not affected
-
Retrieve the installed Prisma Access Agent versionRight-click on Prisma Access Agent in Programs and Features and select Properties, or navigate to the installation directory (typically C:\Program Files\Palo Alto Networks\Prisma Access Agent\) and check the version property of the executableAffected if The displayed version is lower than 26.2.1 (for example, 26.2.0, 26.1.x, or earlier)
-
Confirm the DLP component is presentCheck for DLP-related processes running under the Prisma Access Agent service, or look for DLP-specific files or folders within the Prisma Access Agent installation directoryAffected if The DLP component module or service is found and running as part of the Prisma Access Agent installation
-
Verify local authenticated user access contextReview which Windows user accounts have local logon rights to the endpoint using 'lusrmgr.msc' or 'net user' command, and check if standard user or admin accounts are active on the systemAffected if Any local or domain-authenticated user account can log on to the Windows endpoint where Prisma Access Agent with DLP is installed
A user is affected if Prisma Access Agent with the DLP component is installed at a version lower than 26.2.1 and a local authenticated user has access to that Windows endpoint.
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 from Palo Alto Networks for the Prisma Access Agent. Until patch availability, implement compensating controls such as enhanced endpoint monitoring and user access restrictions on sensitive systems.
26.2.1
- Open the Prisma Access Agent application on the Windows machine
- Navigate to the settings or about section to verify the current version number
- Download Prisma Access Agent version 26.2.1 or later from the official Palo Alto Networks support portal
- Install the updated version following standard installation procedures
- Restart the Prisma Access Agent service if required
- Verify the installed version shows 26.2.1 or later
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
- Implementation2.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0278 — 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-0278 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