ChromeWeb browser · Google
CVE-2026-13886
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 · uneditedInsufficient policy enforcement in Isolated Web Apps in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass content security policy via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceInsufficient policy enforcement in Chrome's Isolated Web Apps feature allowed a remote attacker to bypass Content Security Policy (CSP) via a crafted HTML page. The vulnerability existed because the Isolated Web Apps implementation did not properly enforce CSP restrictions, potentially allowing malicious content to execute with elevated privileges or bypass security restrictions.
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
ChromeWeb browser
< 150.0.7871.46CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Check installed Chrome versionNavigate to chrome://settings/help or use 'Help > About Google Chrome' in the Chrome menu to view the installed version numberAffected if The displayed version is lower than 150.0.7871.46
-
Verify Isolated Web Apps usageCheck if Isolated Web Apps are deployed in your environment by examining Chrome Enterprise policies or looking for IWA-installed directories in the user's AppData folder (typically %LOCALAPPDATA%\Google\Chrome\User Data\IsolatedWebApps)Affected if Isolated Web Apps are installed or enabled and the Chrome version is below 150.0.7871.46
-
Inspect CSP enforcementLoad a test page with a strict CSP policy within an Isolated Web App context and verify whether the CSP headers are properly enforced or can be bypassedAffected if CSP restrictions are not being enforced or can be bypassed in the Isolated Web App context, indicating the vulnerability may be present
You are affected if Chrome version is below 150.0.7871.46 and Isolated Web Apps with potential malicious content are in use, as the CSP bypass could allow unauthorized script execution with elevated privileges.
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 · scoped150.0.7871.46
Update Google Chrome to version 150.0.7871.47 or later. Organizations using Isolated Web Apps should verify their deployment and ensure all instances are running the patched Chrome version.
Chrome 150.0.7871.47 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Chrome will check for updates automatically - if version is below 150.0.7871.47, click 'Update Google Chrome'
- Restart the browser after the update completes
- Verify the version by returning to Settings > Help > About Google Chrome and confirm the version is 150.0.7871.47 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13886 — 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-13886 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