Palo Alto Networks published advisory PAN-SA-2026-0014 on 2026-11-11. It covers 62 Chromium security fixes that the company incorporated into Prisma Browser. The advisory lists the overall severity as High. The vendor is not aware of any malicious exploitation of these issues.
Advisory details
- Advisory: PAN-SA-2026-0014, Chromium: Monthly Vulnerability Update (November 2026).
- Published and updated: 2026-11-11.
- Discovered: externally.
- Product: Prisma Browser.
- Severity: High, CVSS 4.0 CVSS-BT 7.7 and CVSS-B 9.4.
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U/AU:N/R:U/V:D/RE:M/U:Amber.
- Suggested urgency: Moderate. Exploit maturity: Unreported. Response effort: Moderate. Recovery: User. Value density: Diffuse.
- Required configuration: no special configuration is required to be affected.
- Workarounds and mitigations: none known.
- Exploitation status: Palo Alto Networks is not aware of any malicious exploitation.
The advisory cites six Google Chrome stable channel release notes, from October and November 2026, as the origin of the fixes.
Affected and unaffected versions
The advisory's Product Status table reads as follows, exactly as published.
| Versions | Affected | Unaffected |
|---|---|---|
| Prisma Browser | < 155.16.6.80 | >= 157.19.4.39 |
The advisory's CPE data lists Prisma Browser from 157.19.4 up to, but not including, 157.19.4.39 as vulnerable.
CVE list and fixed builds
The Solution table names the first Prisma Browser build that fixes each CVE. The tables below combine it with the advisory's CVE summaries. They are grouped by fixed build, and every row is kept. Prisma Browser 157.19.4.39 or later contains every fix listed.
CVEs fixed in Prisma Browser 155.16.6.80 (37)
| CVE | Summary | Prisma Browser fixed build |
|---|---|---|
| CVE-2026-110136 | Use after free in PDF | 155.16.6.80 |
| CVE-2026-110137 | Use after free in WebRTC | 155.16.6.80 |
| CVE-2026-110138 | Use after free in ShapeDetection | 155.16.6.80 |
| CVE-2026-110139 | Use after free in Media | 155.16.6.80 |
| CVE-2026-110140 | Type confusion in V8 | 155.16.6.80 |
| CVE-2026-110141 | Observable discrepancy in Media | 155.16.6.80 |
| CVE-2026-110142 | Use after free in FileSystem | 155.16.6.80 |
| CVE-2026-110143 | Use of uninitialized variable in ThirdParty lmza_sdk | 155.16.6.80 |
| CVE-2026-110144 | Incorrect authorization in Mojo | 155.16.6.80 |
| CVE-2026-110145 | Use after free in Passwords | 155.16.6.80 |
| CVE-2026-110146 | Information leak in Passwords | 155.16.6.80 |
| CVE-2026-110147 | Use after free in PDF | 155.16.6.80 |
| CVE-2026-110148 | Use after free in SVG | 155.16.6.80 |
| CVE-2026-110149 | Use after free in Browser | 155.16.6.80 |
| CVE-2026-110150 | Privilege elevation in Installer | 155.16.6.80 |
| CVE-2026-110151 | Use after free in Media | 155.16.6.80 |
| CVE-2026-110152 | Buffer overflow in ANGLE | 155.16.6.80 |
| CVE-2026-110153 | Use after free in Media | 155.16.6.80 |
| CVE-2026-110154 | Use after free in Canvas | 155.16.6.80 |
| CVE-2026-110155 | Buffer overflow in PDFium | 155.16.6.80 |
| CVE-2026-110156 | Incorrect reference resolution in Extensions | 155.16.6.80 |
| CVE-2026-110157 | Use after free in SVG | 155.16.6.80 |
| CVE-2026-110158 | Use after free in Passwords | 155.16.6.80 |
| CVE-2026-110159 | Incorrect authorization in Updater | 155.16.6.80 |
| CVE-2026-110160 | Missing authorization in ReadingMode | 155.16.6.80 |
| CVE-2026-110161 | Use after free in Network | 155.16.6.80 |
| CVE-2026-110162 | Use after free in Desktop | 155.16.6.80 |
| CVE-2026-110163 | Use after free in DOM | 155.16.6.80 |
| CVE-2026-110164 | Use after free in DOM | 155.16.6.80 |
| CVE-2026-110165 | Use after free in Core | 155.16.6.80 |
| CVE-2026-110166 | Buffer overflow in Animation | 155.16.6.80 |
| CVE-2026-110167 | Use after free in Media | 155.16.6.80 |
| CVE-2026-110168 | Use after free in V8 | 155.16.6.80 |
| CVE-2026-110169 | Use after free in V8 | 155.16.6.80 |
| CVE-2026-110170 | Use after free in Bindings | 155.16.6.80 |
| CVE-2026-110171 | Use after free in Media | 155.16.6.80 |
| CVE-2026-110172 | Use after free in Media | 155.16.6.80 |
CVEs fixed in Prisma Browser 155.16.7.85 (10)
| CVE | Summary | Prisma Browser fixed build |
|---|---|---|
| CVE-2026-110913 | Memory corruption in DOM | 155.16.7.85 |
| CVE-2026-110914 | Memory corruption in Workers | 155.16.7.85 |
| CVE-2026-110915 | Use after free in Compositing | 155.16.7.85 |
| CVE-2026-110916 | Improper input validation in Desktop | 155.16.7.85 |
| CVE-2026-110917 | Memory corruption in SVG | 155.16.7.85 |
| CVE-2026-110918 | Memory corruption in Core | 155.16.7.85 |
| CVE-2026-110919 | Use after free in V8 | 155.16.7.85 |
| CVE-2026-110920 | Memory corruption in V8 | 155.16.7.85 |
| CVE-2026-110921 | Use after free in V8 | 155.16.7.85 |
| CVE-2026-110922 | Use after free in Prerender | 155.16.7.85 |
CVEs fixed in Prisma Browser 156.17.7.48 (7)
| CVE | Summary | Prisma Browser fixed build |
|---|---|---|
| CVE-2026-113022 | Memory corruption in PDFium | 156.17.7.48 |
| CVE-2026-113142 | Memory corruption in Extensions | 156.17.7.48 |
| CVE-2026-113147 | Improper input validation in WebShare | 156.17.7.48 |
| CVE-2026-113330 | Memory corruption in CustomTabs | 156.17.7.48 |
| CVE-2026-113331 | Memory corruption in Controls | 156.17.7.48 |
| CVE-2026-113343 | Memory corruption in Sandbox | 156.17.7.48 |
| CVE-2026-120931 | Out of bounds write in WebGL | 156.17.7.48 |
CVEs fixed in Prisma Browser 156.17.8.74 (1)
| CVE | Summary | Prisma Browser fixed build |
|---|---|---|
| CVE-2026-118359 | Memory corruption in V8 | 156.17.8.74 |
CVEs fixed in Prisma Browser 156.17.9.80 (2)
| CVE | Summary | Prisma Browser fixed build |
|---|---|---|
| CVE-2026-76027 | Memory corruption in CacheStorage | 156.17.9.80 |
| CVE-2026-76031 | Use after free in Input | 156.17.9.80 |
CVEs fixed in Prisma Browser 157.19.4.39 (5)
| CVE | Summary | Prisma Browser fixed build |
|---|---|---|
| CVE-2026-121166 | Type confusion in PDFium | 157.19.4.39 |
| CVE-2026-121185 | Use after free in PictureInPicture | 157.19.4.39 |
| CVE-2026-121233 | Type confusion in CacheStorage | 157.19.4.39 |
| CVE-2026-121238 | Use after free in Source | 157.19.4.39 |
| CVE-2026-121255 | Incorrect authorization in Autofill AI | 157.19.4.39 |
CVE-2026-110136 in detail
NVD describes CVE-2026-110136 as a use after free in the PDF component of Google Chrome before 155.0.8059.79. A remote attacker could run arbitrary code outside the sandbox through a crafted HTML page. Chromium rates its own severity as Critical.
NVD lists a CVSS 3.1 score of 9.6 (Critical) from CISA-ADP, with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. The weakness is CWE-416, Use After Free. NVD lists no CVSS 4.0 score. The Prisma Browser fix for it shipped in build 155.16.6.80.
Exploitation status
The vendor states that it is not aware of any malicious exploitation of these issues. None of the 62 CVEs is listed in the CISA KEV catalog (catalog version 2026.11.17). Not being in that catalog does not prove that no attacks have occurred.
Terms explained
- Chromium: the open-source browser project behind Google Chrome. Palo Alto Networks incorporated Chromium security fixes into Prisma Browser.
- Use after free (CWE-416): a memory bug. A program keeps using memory after it has released it. An attacker may be able to place their own data there.
- Type confusion: code treats data as a different type than it really is. This can corrupt memory.
- Sandbox: a browser security boundary that limits what web content can do. Code running outside it has more access to the system.
- V8, PDFium and ANGLE: Chromium components. V8 runs JavaScript, PDFium renders PDF files and ANGLE translates graphics calls.
- CVSS-B and CVSS-BT: CVSS 4.0 scores. B is the base score. BT adds threat data, here exploit maturity E:U (Unreported), which lowers 9.4 to 7.7.
- AV:N, AC:L, AT:N, PR:N: attack over the network, low complexity, no special attack requirements, no privileges needed.
- UI:P (CVSS 4.0) and UI:R (CVSS 3.1): user interaction is needed. Passive means the user only has to load content, such as visiting a page.
- VC, VI, VA and SC, SI, SA: impact on confidentiality, integrity and availability of the browser itself and of subsequent systems. All are High.
- S:C (CVSS 3.1): scope changed. The impact reaches beyond the vulnerable component.
- AU, R, V, RE, U: CVSS 4.0 supplemental metrics. Not automatable, user recovery, diffuse value density, moderate response effort and Amber urgency.
What This Means for IT Teams
Organisations that deploy Prisma Browser to their users are in scope. The vendor says no special configuration is needed to be affected, and it lists no workaround.
Check the installed Prisma Browser version on managed devices. Builds at or above 157.19.4.39 include every fix in this advisory, so that is the build to target. Tracking the rollout through endpoint management keeps the version check in one place.
A successful attack needs a user to load malicious content, such as a crafted web page. The vendor reports no known malicious use, and none of the CVEs appears in the CISA KEV catalog.
NVD cross-check
- Agrees: the CVE ID, the use after free in PDF summary and the CWE-416 weakness.
- Differs: NVD scores the Chrome flaw with CVSS 3.1 at 9.6 (Critical). Palo Alto Networks scores its Prisma Browser advisory with CVSS 4.0 at 7.7 (BT) and 9.4 (B).
- Scope: the NVD record and its CPE data cover Google Chrome before 155.0.8059.79. They do not mention Prisma Browser.
Related coverage: Microsoft Edge fixes Chromium use-after-free CVE-2026-126919 (CVSS 8.8).


