dbcve.org
ChromeWeb browser · Google

CVE-2026-7919

HIGH · 8.3 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Use after free in Aura in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidence

Use after free vulnerability in Chrome's Aura UI framework allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a crafted HTML page. The vulnerability exists in versions prior to 148.0.7778.96.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later to obtain the patched binary. Organizations should deploy browser updates through their patch management systems.

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:< 148.0.7778.96

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or use 'About Google Chrome' in the Chrome menu to view the current version number
    Affected if The displayed version is lower than 148.0.7778.96 (for example, 147.x.x.x or earlier)
  2. Verify Chrome build channel
    Check if Chrome is on Stable, Beta, Dev, or Canary channel via chrome://settings/help - the channel is displayed below the version number
    Affected if Running on Stable channel with version < 148.0.7778.96, as this is the primary affected release channel
  3. Confirm Aura UI framework is active
    The Aura UI framework is integral to Chrome's rendering and is always enabled by default on supported platforms; no manual configuration check is needed - this is the core component where the UAF occurs
    Affected if Using any standard Chrome installation where Aura UI is present (default for all modern Chrome builds)
  4. Check for renderer process compromise indicators
    Review chrome://inducebrowsercrashforrealz or crash reports for unexpected renderer crashes, and monitor for suspicious extensions or renderer process anomalies
    Affected if The renderer process has been compromised prior to visiting the crafted HTML page, as this is a required condition for exploitation

You are affected if Chrome version is below 148.0.7778.96 and the renderer process can be compromised, allowing a crafted page to trigger the Use After Free in Aura UI for sandbox escape.

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 148.0.7778.96 or later
Fixed in 148.0.7778.96
Interim mitigation

Update Google Chrome to version 148.0.7778.96 or later to obtain the patched binary. Organizations should deploy browser updates through their patch management systems.

Recommended fix High confidence

148.0.7778.96 or later (any stable channel version >= 148.0.7778.96)

  1. Open Chrome and navigate to chrome://settings/help or click Help > About Google Chrome to check the current version
  2. If the version displayed is earlier than 148.0.7778.96, click 'Update Google Chrome' to download and install the latest version
  3. Restart Chrome after the update completes to apply the fix

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
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7919 — 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-7919 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