ChromeWeb browser · Google
CVE-2026-10938
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 · uneditedInappropriate implementation in Input in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation 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 · moderate confidenceInappropriate implementation in Chrome's Input component allowed a remote attacker who had already compromised the renderer process to bypass site isolation protections via a crafted HTML page. Site isolation is a security feature that separates content from different websites into separate processes to prevent cross-site attacks.
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 installed Chrome versionNavigate to chrome://version in the Chrome browser address bar, or run 'google-chrome --version' (Linux) or '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' (Windows) in command promptAffected if The version displayed is lower than 149.0.7827.53
-
Confirm Chrome is the active browserVerify the browser being used is Google Chrome, not a Chromium-based alternative like Microsoft Edge, Brave, or OperaAffected if Google Chrome specifically is in use (Chromium-based alternatives have separate version tracking and patching cycles)
-
Verify site isolation statusNavigate to chrome://flags/#enable-site-per-process and check if site isolation is enabled, or check Group Policy settings under Computer Configuration > Administrative Templates > Google Chrome > Site IsolationAffected if Site isolation has been disabled or overridden (vulnerability exploits site isolation bypass, so if it's already off the bypass has no effect, but the underlying vulnerable code still exists)
You are affected if Google Chrome version is below 149.0.7827.53 AND site isolation is enabled (the default state). The vulnerability requires site isolation to be active for the bypass to be meaningful.
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 vulnerable Input component implementation.
Chrome 149.0.7827.53 or later
- 1. Open Google Chrome browser
- 2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
- 3. The browser will check for updates automatically
- 4. If an update is available, click 'Update Google Chrome'
- 5. Restart the browser to complete the update
- 6. Verify the version by returning to Help > About Google Chrome and confirm the version number is 149.0.7827.53 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
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10938 — 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-10938 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