ChromeWeb browser · Google
CVE-2026-11038
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 Subresource Integrity in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass content security policy via malicious network traffic. (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 · high confidenceInsufficient policy enforcement in Chrome's Subresource Integrity (SRI) implementation allowed remote attackers to bypass Content Security Policy (CSP) via malicious network traffic, potentially enabling unauthorized script or resource loading.
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
< 149.0.7827.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
- 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 Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.Affected if Version is earlier than 149.0.7827.53 (e.g., 149.0.7827.0, 148.x.x.x, etc.)
-
Identify Subresource Integrity usageInspect web pages or web applications served in this Chrome browser. Look for <script> or <link> tags containing the 'integrity' attribute (e.g., integrity="sha256-..."). Use browser DevTools (F12) > Elements tab to search for 'integrity='.Affected if Web pages contain script or link elements with the integrity attribute set, meaning SRI is in use.
-
Confirm CSP with SRI interactionIn Chrome DevTools > Network tab, load a page with SRI-protected resources. Check the Console for any SRI validation errors or CSP violations. Also review the Security panel in DevTools to see active CSP headers.Affected if Content Security Policy headers are present AND SRI-protected subresources are loaded, creating the condition this CVE exploits.
You are affected if your Chrome version is below 149.0.7827.53 AND you load web pages that use Subresource Integrity (integrity attributes on scripts or links) alongside Content Security Policy, enabling the policy bypass.
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.0.7827.53
Update Google Chrome to version 149.0.7827.53 or later to patch the SRI policy enforcement vulnerability.
Chrome 149.0.7827.53 or later
- Open Google Chrome and navigate to Help > About Google Chrome to check the current version
- If the version is earlier than 149.0.7827.53, Chrome should automatically update; click 'Update Google Chrome' if prompted
- Restart Chrome after the update completes
- Verify the version shows 149.0.7827.53 or later after restart
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11038 — 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-11038 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