ChromeWeb browser · Google

CVE-2026-10006

HIGH · 7.5 CVSS v3.1 Published 2026-05-28

Fix available

A fix is available. Upgrade to 148.0.7778.215 / 148.0.7778.216 or later.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges

Official description

NVD · unedited

Race in WebAudio in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Technical summary

dbcve analysis · high confidence

A race condition vulnerability in Google Chrome's WebAudio component allows a remote attacker to execute arbitrary code inside the sandbox through a maliciously crafted HTML page. The vulnerability exists prior to version 148.0.7778.216.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to patch the race condition in WebAudio. In enterprise environments, deploy the update via centralized patch management and verify complete coverage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 148.0.7778.215< 148.0.7778.216

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Google Chrome is installed

Check for Chrome executable: Windows: %ProgramFiles%\Google\Chrome\Application\chrome.exe or %LocalAppData%\Google\Chrome\Application\chrome.exe; macOS: /Applications/Google Chrome.app; Linux: which google-chrome

Affected if Google Chrome is present on the system
Determine installed Chrome version

Windows: Run 'chrome --version' or right-click chrome.exe > Properties > Details > File version; macOS: Run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'; Linux: Run 'google-chrome --version' or 'chromium --version'

Affected if Version cannot be determined or is lower than 148.0.7778.216
Compare version against affected range

Parse the version number from step 2 and compare numerically against 148.0.7778.216. Note: Both 148.0.7778.215 and 148.0.7778.216 are listed as affected thresholds

Affected if Installed version is less than 148.0.7778.216 (e.g., 148.0.7778.215, 148.0.7778.100, etc.)
Confirm WebAudio is accessible

WebAudio is enabled by default in Chrome. No user action required - the feature is part of the browser's HTML5 capabilities accessible via any webpage

Affected if WebAudio is functional and accessible in the browser (default state)

User is affected if Google Chrome is installed with a version lower than 148.0.7778.216 and the browser can render HTML content with WebAudio capabilities.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 148.0.7778.215 / 148.0.7778.216 or later

Fixed in 148.0.7778.215148.0.7778.216

Interim mitigation

Update Google Chrome to version 148.0.7778.216 or later to patch the race condition in WebAudio. In enterprise environments, deploy the update via centralized patch management and verify complete coverage.

Recommended fix High confidence

148.0.7778.216 or later

Open Chrome browser and click the three-dot menu icon in the top-right corner
Select 'Help' from the dropdown menu
Click 'About Google Chrome'
Chrome will automatically check for updates
If version 148.0.7778.216 or later is available, click 'Update Google Chrome'
Restart the browser to apply the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA2.0 h

10.0 hours of engineering $1,780

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-10006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

chromereleases.googleblog.comRelease Notes
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10006 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-10006?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to 148.0.7778.215 / 148.0.7778.216 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 10 hrs · Moderate

Typical engagement from $1,780

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-10006 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References