CVE-2026-0237: Prisma Browser Auth Bypass Vulnerability

CVE-2026-0237 Overview

CVE-2026-0237 is an improper protection of alternate path vulnerability [CWE-424] in Palo Alto Networks Prisma® Browser on macOS. The browser fails to properly restrict access to an internal automation bridge. A locally authenticated non-admin user can leverage the exposed communication channel to send unauthorized commands to the browser. This action bypasses security controls enforced by the browser.

The issue carries a CVSS 4.0 base score of 7.3 and is tracked under the local attack vector. Palo Alto Networks published the advisory on May 13, 2026.

Critical Impact

A local non-admin user can issue unauthorized commands to Prisma Browser through an unprotected automation bridge, undermining browser-enforced security controls and risking confidentiality, integrity, and availability of browser-managed data.

Affected Products

• Palo Alto Networks Prisma® Browser on macOS
• Refer to the Palo Alto Networks Advisory for specific affected versions
• Non-macOS Prisma Browser builds are not identified as affected in the advisory

Discovery Timeline

• 2026-05-13 - CVE-2026-0237 published to NVD
• 2026-05-13 - Last updated in NVD database

Technical Details for CVE-2026-0237

Vulnerability Analysis

The vulnerability resides in how Prisma Browser exposes an internal automation bridge on macOS. Automation bridges are communication channels that allow trusted components to drive browser behavior programmatically. Prisma Browser does not adequately restrict who can connect to this bridge on the local system. As a result, a process running under a standard non-admin user account can reach the bridge endpoint.

Once connected, the local user can issue commands that the browser treats as originating from a trusted automation source. These commands can manipulate browser state, alter security-relevant settings, or extract data the browser handles. The flaw maps to CWE-424, improper protection of alternate path, where an intended access boundary is reachable through a secondary channel that lacks equivalent controls.

Root Cause

The root cause is missing access enforcement on the alternate path that exposes the automation bridge. The browser assumes the channel is only reachable by privileged or trusted local components. No additional authentication, capability check, or process-identity validation gates command execution. Any local user session with the ability to open the bridge endpoint inherits automation privileges.

Attack Vector

Exploitation requires local access and low privileges. The attacker authenticates as a standard user on a macOS host running the affected Prisma Browser. The attacker connects a custom client to the automation bridge endpoint exposed by the browser process. They then send automation commands that the browser executes outside the normal user-consent and policy boundary. User interaction is not required. The result is unauthorized control over browser actions and access to data the browser protects.

No verified public proof-of-concept code is available. See the Palo Alto Networks Advisory for vendor-provided technical details.

Detection Methods for CVE-2026-0237

Indicators of Compromise

• Unexpected local processes opening connections to the Prisma Browser automation bridge socket or port
• Prisma Browser executing navigation, extension, or configuration changes that do not correlate with user activity
• New or modified launch agents and helper binaries under user-writable paths interacting with the browser
• Outbound network requests initiated by Prisma Browser to domains not associated with user-driven browsing

Detection Strategies

• Inspect macOS endpoint telemetry for non-browser processes establishing inter-process communication with Prisma Browser
• Correlate browser configuration changes with the parent process and user session that triggered them
• Baseline normal automation activity for Prisma Browser and alert on deviations from that baseline

Monitoring Recommendations

• Enable verbose endpoint process and IPC logging on macOS systems where Prisma Browser is deployed
• Forward browser audit logs and macOS Endpoint Security Framework events to a central analytics platform
• Review privileged automation events on a recurring cadence until affected hosts are patched

How to Mitigate CVE-2026-0237

Immediate Actions Required

• Inventory all macOS endpoints running Palo Alto Networks Prisma® Browser and identify affected versions per the vendor advisory
• Apply the fixed Prisma Browser release published by Palo Alto Networks as soon as it is available in your environment
• Restrict local interactive access on shared macOS hosts where Prisma Browser is installed
• Audit recent Prisma Browser activity for signs of unauthorized automation commands

Patch Information

Palo Alto Networks has published remediation guidance in the Palo Alto Networks Advisory. Administrators should consult the advisory for the fixed version of Prisma Browser on macOS and deploy the update through their standard macOS software management workflow.

Workarounds

• Limit Prisma Browser installation to single-user macOS endpoints where no untrusted local accounts exist
• Enforce least-privilege account policies so non-admin users cannot run arbitrary client binaries that could reach the bridge
• Monitor for and block unauthorized helper processes attempting to interface with the browser until the patch is deployed

# Identify Prisma Browser installations and versions on macOS endpoints
mdfind "kMDItemCFBundleIdentifier == 'com.paloaltonetworks.prismabrowser'"
system_profiler SPApplicationsDataType | grep -A 4 -i "Prisma"