ChromeWeb browser · Google
CVE-2026-8577
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 · uneditedInteger overflow in Fonts in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceInteger overflow vulnerability in Google Chrome's Fonts component allows a remote attacker to execute arbitrary code via a crafted HTML page. The vulnerability exists in versions prior to 148.0.7778.168, and while code execution occurs, it is constrained within Chrome's sandbox environment.
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.168CVSS 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.
-
Check Google Chrome version via browser UIOpen Google Chrome, type 'chrome://settings/help' in the address bar and press Enter, or click the three-dot menu > Help > About Google ChromeAffected if The version displayed is earlier than 148.0.7778.168 (for example, 148.0.7778.100 or lower)
-
Check Google Chrome version via command lineWindows: Open Command Prompt and run 'chrome --version'. macOS: Open Terminal and run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'. Linux: Run 'google-chrome --version' in a terminalAffected if The returned version number is less than 148.0.7778.168
-
Confirm active browser useIdentify whether users in the environment actively use Google Chrome to browse web pages, as exploitation requires a user to visit a crafted HTML pageAffected if Google Chrome versions below 148.0.7778.168 are in regular use and users may visit untrusted web content
A user is affected if their installed Google Chrome version is below 148.0.7778.168 and they use the browser to browse web pages, since exploitation occurs through viewing a crafted HTML page
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.168
Update Google Chrome to version 148.0.7778.168 or later to patch the integer overflow in the Fonts component.
Chrome 148.0.7778.168 or later
- Open Google Chrome and navigate to chrome://settings/help or go to Settings > About Chrome
- Chrome will automatically check for available updates
- If the update to version 148.0.7778.168 or later is available, click 'Update Chrome' to download and install it
- After the update completes, restart Google Chrome to apply the changes
- Verify the version by returning to chrome://settings/help - it should show 148.0.7778.168 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8577 — 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-8577 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