dbcve.org
CWE-754Weakness · CWE-754

CVE-2025-0129

CRITICAL · 9.3 CVSS v4.0 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
No privileges 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
An improper exception check in Palo Alto Networks Prisma Access Browser allows a low privileged user to prevent Prisma Access Browser from applying it's Policy Rules. This enables the user to use Prisma Access Browser without any restrictions.

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

An improper exception check in Palo Alto Networks Prisma Access Browser allows authenticated low-privileged users to bypass policy rule enforcement. By manipulating exception handling, users can prevent the browser from applying configured security policies, effectively using the browser without any restrictions.

MitigationApply the vendor-supplied security patch for Prisma Access Browser to correct the improper exception check. Verify that policy rules are properly enforced after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Authentication
None
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:L/U:Amber

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. Identify if Prisma Access Browser is installed
    Check for Prisma Access Browser installation in common program directories (e.g., C:\Program Files\Palo Alto Networks\Prisma Access Browser on Windows, or /Applications/Prisma Access Browser on macOS). On Windows, also check Add/Remove Programs or the registry for installed software named 'Prisma Access Browser'.
    Affected if Prisma Access Browser is not installed on the system
  2. Determine the installed Prisma Access Browser version
    Right-click the Prisma Access Browser application and select 'Properties', then view the 'Details' tab for the version number. Alternatively, launch the browser and navigate to chrome://version or help/about to retrieve the version information.
    Affected if The installed version matches or falls within an unpatched version range for CVE-2025-0129 (compare against vendor advisories for specific affected versions)
  3. Verify policy enforcement is active
    Review Prisma Access Browser security policy configurations through the Prisma Access admin console. Check if browser policies are defined and pushed to the browser client. Confirm that policy rules are in an 'active' or 'enforced' state.
    Affected if Policy rules show as not being applied or enforced, or an exception condition is reported in the admin console logs
  4. Check admin console for exception events
    Access the Prisma Access admin portal and review browser-related logs or event logs for exception errors, policy bypass indicators, or failed policy enforcement attempts. Look for entries indicating policy rule failures or exception conditions triggered by low-privileged users.
    Affected if Exception events or policy enforcement failures are logged, particularly for low-privileged authenticated users
  5. Confirm user privilege level
    Through the Prisma Access admin console, verify the privilege level of the affected user account(s). Determine if the user has only standard or low-privileged access rather than administrative privileges.
    Affected if A low-privileged authenticated user can trigger the exception condition and bypass policy enforcement

A user is affected if Prisma Access Browser is installed with an unpatched version and low-privileged users can trigger exception conditions that prevent security policies from being applied.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied security patch for Prisma Access Browser to correct the improper exception check. Verify that policy rules are properly enforced after the update.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0129 — 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-2025-0129 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