Prisma BrowserApplication · Paloaltonetworks
CVE-2026-0275
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 · uneditedA local privilege escalation vulnerability in Palo Alto Networks Prisma® Browser allows a locally authenticated administrator with access to the macOS local filesystem to perform actions on the device with root privileges. This issue only affects Prisma® Browser on macOS.
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 confidenceA local privilege escalation vulnerability in Palo Alto Networks Prisma Browser on macOS allows a locally authenticated administrator with filesystem access to perform actions with root privileges due to improper privilege management in the application.
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
< 149.10.3.53CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Confirm Prisma Browser is installed on macOSCheck /Applications folder for 'Prisma Browser.app' or run: ls /Applications | grep -i prismaAffected if Prisma Browser application exists on the system
-
Determine installed Prisma Browser versionRight-click Prisma Browser.app > Get Info, or run: defaults read /Applications/Prisma\ Browser.app/Contents/Info CFBundleShortVersionStringAffected if Application is present and version can be retrieved
-
Compare installed version to vulnerable rangeCheck if the retrieved version number is less than 149.10.3.53Affected if Installed version is 149.10.3.52 or lower, or any version that reports as less than 149.10.3.53
-
Verify user has administrator privileges on the systemCheck current user privileges via: whoami && groups | grep admin, or System Preferences > Users & Groups shows admin roleAffected if The user account running Prisma Browser is a member of the admin group on the macOS host
User is affected if Prisma Browser is installed on macOS with a version lower than 149.10.3.53 AND the user has administrator-level access to the system.
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 · scoped149.10.3.53
Apply vendor-provided patches when available; limit administrative access to trusted personnel and monitor for unauthorized privilege escalation attempts until a patch is deployed.
149.10.3.53 or later
- Upgrade Prisma Browser to version 149.10.3.53 or later on macOS systems
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
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0275 — 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-0275 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