ChromeWeb browser · Google
CVE-2026-13877
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 · uneditedInsufficient validation of untrusted input in ANGLE in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory 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 · high confidenceThis is an information disclosure vulnerability in Google's ANGLE graphics library within Chrome. A remote attacker who has already compromised the browser's renderer process can exploit insufficient input validation via a crafted HTML page to read sensitive data from process memory. The attack requires pre-existing code execution in the renderer, lowering the practical exploitability from pure remote attack.
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
< 150.0.7871.46CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome installationOn Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On Mac, check /Applications/Google Chrome.app. On Linux, run which google-chrome or check /usr/bin/google-chrome.Affected if Google Chrome is installed on the system.
-
Retrieve installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line on Linux. On Windows, you can also right-click chrome.exe and select Properties > Details to view the File Version.Affected if A version number is returned.
-
Compare version against vulnerable rangeCompare the installed version number to 150.0.7871.46. Note that versions prior to 150.0.7871.46 are affected (e.g., 150.0.7871.0, 149.x.x.x, 148.x.x.x, etc.).Affected if The installed version is less than 150.0.7871.46.
-
Assess renderer compromise riskThis vulnerability requires an attacker who already has code execution within the Chrome renderer process. Review any suspicious browser extensions, compromised websites visited, or indicators of renderer process compromise.Affected if The browser renderer process has been compromised and the Chrome version is below 150.0.7871.46.
The environment is affected if Google Chrome is installed with a version lower than 150.0.7871.46 AND an attacker has already achieved code execution in the browser's renderer process.
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 · scoped150.0.7871.46
Update Google Chrome to version 150.0.7871.47 or later. In clinical environments, verify compatibility with clinical systems before deployment and ensure browser update mechanisms are functioning across all endpoints.
Chrome 150.0.7871.47 or later
- 1. Open Google Chrome browser
- 2. Navigate to Chrome Menu > Help > About Google Chrome
- 3. The browser will automatically check for updates
- 4. If an update is available, click 'Update Google Chrome'
- 5. Restart the browser to apply the update
- 6. Verify the version by returning to Help > About Google Chrome and confirm version 150.0.7871.47 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13877 — 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-13877 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