dbcve.org
ChromeWeb browser · Google

CVE-2026-5896

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 147.0.7727.55 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Policy bypass in Audio in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who convinced a user to engage in specific UI gestures to bypass sandbox download restrictions via a crafted HTML page. (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 · moderate confidence

A policy bypass vulnerability in Chrome's Audio component allowed a remote attacker to bypass sandbox download restrictions by tricking users into performing specific UI gestures on a crafted HTML page. The attack required user interaction (specific UI gestures) and resulted in a sandbox restriction bypass rather than direct code execution.

MitigationUpdate Google Chrome to version 147.0.7727.55 or later to patch this vulnerability. Users should avoid interacting with untrusted UI gestures on suspicious web pages as an additional precaution.

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
Affected:< 147.0.7727.55

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify installed Chrome version
    Navigate to chrome://settings/help or click Help > About Google Chrome to view the current version number
    Affected if The displayed version is lower than 147.0.7727.55 (e.g., 147.0.7727.0, 146.x.x.x, etc.)
  2. Confirm Audio component is in use
    The vulnerability exists in Chrome's Audio component. No special config check needed - Audio APIs (HTML5 Audio, Web Audio API) are enabled by default in Chrome
    Affected if Audio playback features are accessible in Chrome (this is true for default Chrome installations)
  3. Understand attack prerequisites
    This is a sandbox bypass vulnerability requiring user interaction. The attacker must trick the user into performing specific UI gestures (clicks, drags, or other interactions) on a crafted malicious HTML page
    Affected if Users can be persuaded to interact with untrusted web content while browsing
  4. Check if sandbox restrictions matter in your environment
    Review your organization's Chrome security policies or Chrome Enterprise settings related to download restrictions and sandbox enforcement
    Affected if Your environment relies on Chrome's sandbox to restrict downloads from untrusted sources

You are affected if you are running any Google Chrome version below 147.0.7727.55 and users in your environment can be tricked into interacting with malicious web pages that abuse the Audio component to bypass download restrictions.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 147.0.7727.55 or later
Fixed in 147.0.7727.55
Interim mitigation

Update Google Chrome to version 147.0.7727.55 or later to patch this vulnerability. Users should avoid interacting with untrusted UI gestures on suspicious web pages as an additional precaution.

Recommended fix High confidence

Chrome 147.0.7727.55 or later

  1. Open Google Chrome and navigate to Help > About Google Chrome to check the current version
  2. If the version is below 147.0.7727.55, click 'Update Google Chrome' to apply the latest update
  3. Restart Chrome if prompted to complete the update
  4. If automatic update is unavailable, download Chrome 147.0.7727.55 or later from the official Chrome download page (google.com/chrome)
  5. Verify the update was successful by checking Help > About Google Chrome shows version 147.0.7727.55 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5896 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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