dbcve.org
Prisma BrowserApplication · Paloaltonetworks

CVE-2026-0236

HIGH · 7.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 146.10.7.154 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
A code injection vulnerability in Palo Alto Networks Prisma® Browser on macOS fails to properly restrict access to its AppleScript interface allowing a locally authenticated non-admin user to leverage this exposed Apple Event handler to send unauthorized commands to the browser.

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

Palo Alto Networks Prisma Browser for macOS contains a code injection vulnerability where the AppleScript interface is not properly restricted, allowing a locally authenticated non-admin user to send unauthorized commands through the exposed Apple Event handler.

MitigationRestrict access to the Prisma Browser's AppleScript interface by implementing proper authentication and authorization checks before executing AppleScript commands, or disable the exposed Apple Event handler if not required.

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.10.7.154

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
    Check if Palo Alto Networks Prisma Browser exists in /Applications or run: ls /Applications/ | grep -i 'prisma'
    Affected if Prisma Browser is not found in the Applications directory
  2. Determine installed version
    Run: defaults read /Applications/Prisma\ Browser.app/Contents/Info.plist CFBundleShortVersionString OR right-click the app in Finder > Get Info to view the Version field
    Affected if Version is present but lower than 146.10.7.154 (e.g., 146.10.7.153 or earlier)
  3. Check if AppleScript/Apple Event handler is exposed
    Run: osascript -e 'tell application "Prisma Browser" to return name' to test if the app responds to AppleScript commands. Also inspect the app's Info.plist for NSAppleEventsUsageDescription and OSAApplet.entitlements for any AppleScript-related configurations.
    Affected if The application responds to AppleScript commands without requiring admin authentication, indicating the Apple Event handler is exposed

You are affected if Prisma Browser is installed with a version lower than 146.10.7.154 AND the AppleScript/Apple Event interface is accessible without proper authorization.

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.10.7.154 or later
Fixed in 146.10.7.154
Interim mitigation

Restrict access to the Prisma Browser's AppleScript interface by implementing proper authentication and authorization checks before executing AppleScript commands, or disable the exposed Apple Event handler if not required.

Recommended fix High confidence

146.10.7.154 or later

  1. Identify current Prisma Browser version on macOS systems by opening the browser and checking About section
  2. Download Prisma Browser version 146.10.7.154 or later from the official Palo Alto Networks download portal
  3. Install the updated Prisma Browser over the existing installation
  4. Verify the installed version shows 146.10.7.154 or higher in the browser's About section
  5. Confirm the browser starts and operates normally after the upgrade

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

Fix this in Prisma Browser Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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