ChromeWeb browser · Google
CVE-2025-8879
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 libaom in Google Chrome prior to 139.0.7258.127 allowed a remote attacker to potentially exploit heap corruption via a curated set of gestures. (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 vulnerability in libaom (AV1 video codec library) in Google Chrome prior to version 139.0.7258.127 allows remote attackers to potentially exploit heap corruption through a crafted series of video playback interactions (gestures).
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
< 139.0.7258.127CVSS 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 version via browser UIOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on that page.Affected if The displayed version is less than 139.0.7258.127 (for example, 139.0.7258.100 or earlier)
-
Check Chrome version via command line on WindowsRun 'chrome --version' or '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' in Command Prompt or PowerShell.Affected if The reported version is less than 139.0.7258.127
-
Check Chrome version via command line on macOSRun '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal.Affected if The reported version is less than 139.0.7258.127
-
Check Chrome version via command line on LinuxRun 'google-chrome --version' or 'chromium --version' in terminal, depending on how Chrome was installed.Affected if The reported version is less than 139.0.7258.127
If the installed Google Chrome version is below 139.0.7258.127, the environment is affected by this vulnerability and could be exploited when processing malicious AV1 video content.
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 · scoped139.0.7258.127
Update Google Chrome to version 139.0.7258.127 or later to patch the libaom heap buffer overflow.
Chrome 139.0.7258.127 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Alternatively, navigate to chrome://settings/help in the address bar
- Chrome will automatically check for updates and download version 139.0.7258.127 or later
- Restart Chrome to complete the installation of the updated version
- Verify the version by returning to chrome://settings/help and confirming the version is 139.0.7258.127 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
- 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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8879 — 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-2025-8879 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