ChromeWeb browser · Google
CVE-2026-10894
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 · uneditedUse after free in Printing in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
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 confidenceUse after free vulnerability in Google Chrome's printing component on Linux (versions prior to 149.0.7827.53). A remote attacker who has already compromised the renderer process can exploit this memory corruption bug via crafted HTML pages to potentially escape the Chrome sandbox.
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
< 149.0.7827.53CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome version on LinuxRun 'google-chrome --version' or open Chrome, go to Settings > About Chrome to view the version numberAffected if Version is earlier than 149.0.7827.53 (e.g., 149.0.7827.0, 148.x.x.x, etc.)
-
Confirm operating system is LinuxRun 'uname -a' or check system information. This CVE specifically affects Chrome on Linux, not Windows or macOSAffected if Running Google Chrome on Linux with a vulnerable version
-
Verify Chrome's printing component is accessibleOpen Chrome and attempt to access the print dialog (Ctrl+P or File > Print). The print functionality is a built-in component that is enabled by defaultAffected if Printing functionality is available and the Chrome version is vulnerable
-
Check for unusual Chrome renderer processesRun 'ps aux | grep chrome' or 'top' to monitor for unexpected child processes. A compromised renderer process is required for exploitationAffected if Unusual or suspicious renderer processes are observed alongside a vulnerable version
You are affected if Google Chrome on Linux is installed with a version earlier than 149.0.7827.53 and users can access printing functionality or render HTML content from untrusted sources.
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 · scoped149.0.7827.53
Update Google Chrome for Linux to version 149.0.7827.53 or later. Until updated, restrict access to untrusted HTML content and monitor for suspicious printing activity.
Chrome 149.0.7827.53 or later (stable channel)
- Open Google Chrome
- Navigate to Settings > About Chrome
- Click 'Check for updates' or wait for automatic update check
- If update available, click 'Restart' to apply the update
- Verify the version is 149.0.7827.53 or later by returning to Settings > About Chrome
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-10894 — 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-10894 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