ChromeWeb browser · Google
CVE-2026-7899
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 · uneditedOut of bounds read and write in V8 in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceOut of bounds memory read/write vulnerability in Google Chrome's V8 JavaScript engine allows remote code execution via malicious HTML pages. The vulnerability exists in Chrome versions prior to 148.0.7778.96.
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.96CVSS 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.
-
Open Chrome version pageNavigate to chrome://version in the Chrome address bar and locate the 'Google Chrome' field showing the version number (e.g., 148.0.7778.96)Affected if The version displayed is lower than 148.0.7778.96
-
Check Chrome version via command line (Windows)Run 'chrome --version' or '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' in Command Prompt or PowerShellAffected if The reported version number is less than 148.0.7778.96
-
Check Chrome version via command line (macOS)Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in TerminalAffected if The reported version number is less than 148.0.7778.96
-
Check Chrome version via command line (Linux)Run 'google-chrome --version' or 'chromium --version' in terminalAffected if The reported version number is less than 148.0.7778.96
-
Check via Chrome Settings GUIClick the three-dot menu > Settings > About Chrome. The version is displayed on this page.Affected if The version shown is below 148.0.7778.96
The environment is affected if the installed Google Chrome version is any release prior to 148.0.7778.96, since the V8 engine vulnerability exists in all earlier versions.
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.96
Update Google Chrome to version 148.0.7778.96 or later to patch the V8 engine vulnerability. Organizations should deploy this update through standard patch management processes.
148.0.7778.96 or later
- Open Google Chrome
- Navigate to chrome://settings/help or go to Menu > Settings > About Chrome
- Chrome will automatically check for updates
- If version 148.0.7778.96 or later is available, click 'Update Google Chrome'
- Click 'Relaunch' to restart Chrome and complete the update
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
- 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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7899 — 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-7899 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