ChromeWeb browser · Google
CVE-2026-13026
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 Digital Credentials in Google Chrome on Mac prior to 149.0.7827.197 allowed a remote attacker to potentially exploit heap corruption 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 · high confidenceUse after free vulnerability in Digital Credentials component of Google Chrome on Mac prior to version 149.0.7827.197 allows remote attackers to potentially exploit heap corruption via a specially crafted HTML page.
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.197CVSS 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.
-
Verify the operating system is macOSRun 'sw_vers' or check System Information to confirm the platform is Apple macOS. This vulnerability only affects Chrome on Mac, not other platforms.Affected if The system is running macOS - if running Windows or Linux, this CVE does not apply.
-
Check the installed Google Chrome versionOpen Chrome, navigate to chrome://settings/help, or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' in Terminal to display the installed version number.Affected if The installed version is earlier than 149.0.7827.197 (for example, 149.0.7827.196 or earlier).
-
Verify Digital Credentials component accessIn Chrome on Mac, attempt to access the Digital Credentials settings by navigating to chrome://settings or checking if the browser exposes any Digital Credentials-related UI or API endpoints.Affected if The Digital Credentials feature is present and accessible on the Chrome installation.
A Mac user is affected only if running Google Chrome version earlier than 149.0.7827.197 AND the Digital Credentials component is present and accessible on that system.
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.197
Update Google Chrome to version 149.0.7827.197 or later on all affected Mac systems; enterprises may use MDM or patch management tools to ensure widespread deployment.
Chrome 149.0.7827.197 (stable release)
- 1. Open Google Chrome on Mac
- 2. Click on the Chrome menu in the menu bar
- 3. Select 'About Google Chrome'
- 4. The browser will automatically check for updates and display the current version
- 5. If an update is available to version 149.0.7827.197 or later, click 'Update Google Chrome'
- 6. Restart the browser to apply the update
- 7. Verify the version by returning to 'About Google Chrome' and confirming the version is 149.0.7827.197 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13026 — 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-13026 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