dbcve.org
ChromeWeb browser · Google

CVE-2026-13838

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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 · unedited
Inappropriate implementation in CSS in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)

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 confidence

This is a same-origin policy (SOP) bypass vulnerability in Google Chrome's CSS handling. An attacker could craft a malicious HTML page to exploit improper CSS implementation, allowing them to access resources from different origins that should be restricted by the SOP.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later. Organizations should ensure automatic browser updates are enabled or push the patched version through their endpoint management systems.

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
Affected:< 150.0.7871.47

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or type chrome://version in the address bar. The version number is displayed at the top of the page.
    Affected if The displayed version number is less than 150.0.7871.47 (e.g., 150.0.7871.0, 149.x.x.x, etc.)
  2. Verify Chrome version via command line
    On Windows, open Command Prompt and run: reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLFeature" /v Version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. On Linux, run: google-chrome --version or google-chrome-stable --version.
    Affected if The returned version is lower than 150.0.7871.47
  3. Check if automatic updates are enabled
    Navigate to chrome://settings in Chrome, then go to the "About Chrome" section. Look for the update status and whether automatic updates are turned on or off.
    Affected if Automatic updates are disabled and the current version is below 150.0.7871.47
  4. Confirm the CSS feature is in use
    This vulnerability affects CSS handling in Chrome. Any web page that loads external CSS stylesheets or processes CSS from cross-origin sources could trigger the vulnerable code path. There is no specific configuration to disable; the flaw exists in how Chrome processes CSS.
    Affected if The browser version is vulnerable (< 150.0.7871.47) and the user browses the web or loads any web content with CSS stylesheets.

A user is affected if their Google Chrome browser version is below 150.0.7871.47 and they use the browser to access web content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 150.0.7871.47 or later
Fixed in 150.0.7871.47
Interim mitigation

Update Google Chrome to version 150.0.7871.47 or later. Organizations should ensure automatic browser updates are enabled or push the patched version through their endpoint management systems.

Recommended fix High confidence

150.0.7871.47

  1. Update Google Chrome to version 150.0.7871.47 or later
  2. On desktop, Chrome typically auto-updates; to force an update, go to chrome://settings/help and click 'Update Google Chrome'
  3. If auto-update is unavailable, download the latest version from chrome.com

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13838 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13838 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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