ChromeWeb browser · Google
CVE-2026-11301
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 LiveCaption in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform out of bounds memory access via malicious network traffic. (Chromium security severity: Low)
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 confidenceA memory safety vulnerability in Google Chrome's LiveCaption feature (versions prior to 149.0.7827.53) allows out of bounds memory access when processing malicious network traffic, potentially enabling information disclosure or denial of service.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 if Google Chrome is installedOpen Chrome and navigate to chrome://version, or click Help > About Google Chrome. Note the version number displayed.Affected if Chrome is not installed - not affected by this CVE.
-
Verify the installed Chrome versionIn chrome://version, locate the 'Browser' or 'Version' field. Compare the full version number (e.g., 149.0.7827.53) against the affected threshold.Affected if Version is less than 149.0.7827.53 - potentially affected if LiveCaption is enabled.
-
Confirm LiveCaption feature statusGo to Settings > Accessibility (or type chrome://settings/accessibility in the address bar). Look for the 'Live Caption' toggle under the Media section.Affected if LiveCaption is turned ON - the vulnerability is exploitable in your environment. If OFF, the attack surface is not exposed.
-
Check Chrome channel for update availabilityIn chrome://settings/help, check if Chrome reports 'Chrome is up to date' or shows a pending update. Also verify if your organization manages Chrome updates via group policy.Affected if Chrome reports an older version with pending updates - vulnerable until updated.
You are affected if Google Chrome is installed with a version lower than 149.0.7827.53 AND the LiveCaption feature is enabled in settings.
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 LiveCaption vulnerability; organizations should deploy browser updates through their patch management infrastructure.
Chrome 149.0.7827.53 or later
- Open Google Chrome browser
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates
- If update is available, click 'Update Google Chrome' or wait for it to download
- Restart the browser to apply the update
- Verify the version by returning to About Google Chrome and confirming version 149.0.7827.53 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11301 — 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-11301 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