dbcve.org
Prisma BrowserApplication · Paloaltonetworks

CVE-2026-0237

HIGH · 7.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 146.16.6.165 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
An improper protection of alternate path vulnerability in Palo Alto Networks Prisma® Browser on macOS fails to properly restrict access to an internal automation bridge. This allows a locally authenticated non-admin user to leverage an exposed communication channel to send unauthorized commands to the browser, bypassing security controls.

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 confidence

Palo Alto Networks Prisma Browser on macOS contains an improper protection vulnerability where an internal automation bridge is inadequately secured, allowing a locally authenticated non-admin user to access an exposed communication channel and send unauthorized commands to the browser, effectively bypassing security controls.

MitigationApply the vendor-supplied patch for Prisma Browser when available; in the interim, restrict local user permissions and monitor for unusual automation bridge activity.

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 BrowserApplication
Affected:< 146.16.6.165

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 Browser is installed on macOS
    Check for the presence of /Applications/Prisma Browser.app or search using 'ls /Applications/ | grep -i prisma' in Terminal
    Affected if The application is not found in /Applications/
  2. Identify installed Prisma Browser version
    Run: defaults read /Applications/Prisma\ Browser.app/Contents/Info.plist CFBundleVersion or check via 'Get Info' on the application
    Affected if Version number returned is less than 146.16.6.165 (e.g., 146.16.6.160, 146.16.5.x, etc.)
  3. Confirm user access to automation bridge
    Attempt to access the internal automation bridge endpoint or examine Prisma Browser process arguments for exposed automation interfaces using 'ps aux | grep -i prisma'
    Affected if The automation bridge is accessible or exposed to non-admin local users
  4. Verify non-admin user context
    Run 'whoami' and 'groups' to confirm the current user is not in the admin group, or check if other non-admin users exist on the system
    Affected if A non-admin user account exists and Prisma Browser version is below 146.16.6.165

You are affected if Prisma Browser is installed on macOS with a version lower than 146.16.6.165 and non-admin users can access the exposed internal automation bridge.

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 146.16.6.165 or later
Fixed in 146.16.6.165
Interim mitigation

Apply the vendor-supplied patch for Prisma Browser when available; in the interim, restrict local user permissions and monitor for unusual automation bridge activity.

Recommended fix High confidence

Prisma Browser version 146.16.6.165 or later

  1. Verify current Prisma Browser version by opening the application and navigating to Help > About or checking the application info
  2. Download the latest version of Prisma Browser from the official Palo Alto Networks support portal or authorized distribution channels
  3. Ensure version 146.16.6.165 or later is obtained - this version contains the fix for the improper protection vulnerability
  4. Close any running instances of Prisma Browser before installation
  5. Install the updated version following standard application update procedures
  6. After installation, verify the installed version matches or exceeds 146.16.6.165
  7. Review release notes on security.paloaltonetworks.com for any specific configuration changes required after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prisma Browser Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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