ChromeWeb browser · Google
CVE-2026-11058
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 CredentialProvider in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to perform OS-level privilege escalation 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 confidenceAn integer overflow vulnerability exists in the CredentialProvider component of Google Chrome on Windows versions prior to 149.0.7827.53. An attacker who has already compromised the renderer process can exploit this flaw through a crafted HTML page to achieve OS-level privilege escalation.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Verify Google Chrome is installed on WindowsOpen Command Prompt or PowerShell and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" /ve or check Program Files for chrome.exeAffected if Chrome is installed on the Windows system
-
Determine installed Chrome versionOpen Chrome, go to Settings > About Chrome, or run: chrome --version in command line, or check version in registry under the Chrome App Paths keyAffected if Version number is displayed and can be compared
-
Compare version against affected rangeCompare the installed version number to 149.0.7827.53 using standard version comparisonAffected if Installed version is less than 149.0.7827.53 (e.g., 149.0.7827.0, 148.x.x.x, etc.)
-
Confirm CredentialProvider component contextThis vulnerability targets the CredentialProvider component used by Windows for credential management. Check if Chrome has permissions or access patterns that could interact with Windows credential prompts on this system.Affected if The system uses Windows credential features and Chrome has renderer process access (standard Chrome configuration)
User is affected if running Google Chrome on Windows with version lower than 149.0.7827.53, where the CredentialProvider component is present and the browser can process HTML content (standard configuration).
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
Upgrade Google Chrome for Windows to version 149.0.7827.53 or later to patch the integer overflow vulnerability in the CredentialProvider component.
149.0.7827.53 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version number
- If version is below 149.0.7827.53, Chrome will automatically check for and download updates
- Restart Chrome after the update is downloaded and installed
- Alternatively, download the latest Chrome version from the official Google Chrome website: https://www.google.com/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
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11058 — 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-11058 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