ChromeWeb browser · Google
CVE-2026-9985
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 · uneditedInsufficient validation of untrusted input in Media in Google Chrome on ChromeOS prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory 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 confidenceInsufficient validation of untrusted input in the Media component of Google Chrome on ChromeOS allows a remote attacker with an already-compromised renderer process to read potentially sensitive information from process memory via a crafted HTML page.
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
< 148.0.7778.216CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/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.
-
Verify Chrome browser is running on ChromeOSOpen Chrome browser, click the three-dot menu, select 'Help', then 'About Google Chrome'. Check that the OS is listed as ChromeOS in the browser info or system settings.Affected if The browser is Google Chrome on ChromeOS specifically (not Windows, macOS, or Linux).
-
Find the installed Chrome version numberNavigate to chrome://version in the address bar. Locate the 'Chrome' row which shows the full version string (e.g., 148.0.7778.216).Affected if A version number is displayed in the format X.X.X.X.
-
Compare version against affected rangeTake the installed version number from chrome://version and compare it numerically to 148.0.7778.216. Any version lower than 148.0.7778.216 is affected.Affected if The installed version is less than 148.0.7778.216 (e.g., 148.0.7778.200 or 147.x.x.x).
-
Confirm Media component is accessibleVerify that the browser can process media files. Open a media-heavy website or attempt to play an audio/video file in Chrome.Affected if Media playback functionality is available and the browser is actively used.
A user is affected if they are running Google Chrome on ChromeOS with a version number lower than 148.0.7778.216 and the browser's Media component is functional.
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 · scoped148.0.7778.216
Update Google Chrome on ChromeOS to version 148.0.7778.216 or later to patch the vulnerability.
Chrome 148.0.7778.216 or later (ChromeOS)
- Open Chrome browser on ChromeOS
- Navigate to Settings > Help > About Chrome
- Chrome will automatically check for and install the latest version
- Verify the installed version is 148.0.7778.216 or later
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
- 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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9985 — 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-9985 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