ChromeWeb browser · Google
CVE-2026-3544
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 · uneditedHeap buffer overflow in WebCodecs in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to perform an out of bounds memory write 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 confidenceHeap buffer overflow in Google Chrome's WebCodecs API allows a remote attacker to perform out-of-bounds memory write via a malicious crafted HTML page. This could enable arbitrary code execution or memory corruption on affected clients.
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
< 145.0.7632.159< 145.0.7632.160CVSS 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 installed Chrome versionNavigate to chrome://version or click the three-dot menu > Help > About Google Chrome to view the current version numberAffected if The displayed version is lower than 145.0.7632.159 or 145.0.7632.160 (compare your exact version to these thresholds)
-
Verify WebCodecs API availabilityOpen a new tab, press F12 to open DevTools, go to the Console tab, and type 'typeof VideoDecoder' to check if the WebCodecs API is available in the browserAffected if The command returns a function type (indicating WebCodecs is present) on a vulnerable Chrome version
-
Review browser flags related to WebCodecsNavigate to chrome://flags/#enable-webcodecs and check whether the WebCodecs flag is set to Enabled, Default, or DisabledAffected if WebCodecs is enabled or set to Default on a Chrome version below the patched releases
You are affected if your Chrome version is below 145.0.7632.159 (or 145.0.7632.160 depending on your channel) AND the WebCodecs API is accessible in your browser.
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 · scoped145.0.7632.159145.0.7632.160
Update Google Chrome to version 145.0.7632.159 or later to patch the vulnerability. Organizations should verify WebCodecs functionality after applying the update.
Chrome 145.0.7632.159 or later (or 145.0.7632.160 or later, depending on the specific branch)
- 1. Open Google Chrome browser
- 2. Navigate to Chrome Settings (three-dot menu > Settings)
- 3. Click on 'About Chrome' in the left sidebar
- 4. Chrome will automatically check for updates
- 5. If an update is available, click 'Update Chrome'
- 6. Restart the browser to apply the update
- 7. Verify the version by returning to 'About Chrome' and confirming the version number is 145.0.7632.159 or higher
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
- 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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3544 — 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-3544 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