ChromeWeb browser · Google
CVE-2026-13033
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 · uneditedOut of bounds read and write in Blink>InterestGroups in Google Chrome prior to 149.0.7827.197 allowed a remote attacker to execute arbitrary code 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 confidenceA memory corruption vulnerability in the Blink rendering engine's InterestGroups implementation (used by the Privacy Sandbox/FLEDGE API) allows out-of-bounds read and write operations. A remote attacker can exploit this via a crafted HTML page to achieve arbitrary code execution on the victim's machine.
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.
-
Check installed Chrome versionOpen chrome://version in the Chrome address bar and note the version string, or go to Settings > About ChromeAffected if The version number is less than 149.0.7827.197 (e.g., 149.0.7827.0, 148.x.x.x, etc.)
-
Verify FLEDGE API statusNavigate to chrome://flags/#enable-fledge or go to Settings > Privacy and security > Privacy Sandbox and check if FLEDGE/Interest Groups is enabledAffected if The FLEDGE API or Interest Groups feature is turned ON (the vulnerability only affects environments where this Privacy Sandbox feature is active)
-
Confirm Interest Groups feature flagNavigate to chrome://flags/#enable-tracking-bypass-detection and look for Interest Group-related settings, or check chrome://settings/privacy for Privacy Sandbox APIsAffected if Any Interest Group or FLEDGE-related experimental features are enabled in chrome://flags
A user is affected if they are running Google Chrome version 149.0.7827.197 or earlier AND have the FLEDGE/InterestGroups API enabled (the vulnerability exists in that specific code path).
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. In enterprise environments, deploy the update via patch management and verify completion across all managed endpoints.
149.0.7827.197 or later
- Open Google Chrome browser
- Navigate to chrome://settings/help or click Help > About Google Chrome
- Chrome will automatically check for updates
- If update is available, click 'Update Google Chrome' to download and install it
- Restart the browser to complete the update
- Verify the version is 149.0.7827.197 or later by returning to chrome://settings/help
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
- 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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13033 — 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-13033 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