ChromeWeb browser · Google
CVE-2024-6994
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 · uneditedHeap buffer overflow in Layout in Google Chrome prior to 127.0.6533.72 allowed a remote attacker to potentially exploit heap corruption 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 confidenceHeap buffer overflow vulnerability in Google Chrome's Layout component allows remote attackers to exploit heap corruption via a crafted HTML page. The flaw exists in versions prior to 127.0.6533.72 and could enable arbitrary code execution or crash the browser.
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
< 127.0.6533.72CVSS 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.
-
Open Chrome version informationIn the Chrome browser, click the three-dot menu in the top-right corner, select 'Help', then select 'About Google Chrome'. The version number will display on this page.Affected if The displayed version number is lower than 127.6533.72
-
Verify the full version stringOn the About Google Chrome page, note the complete version string (for example: 127.0.6533.70). Compare each numeric segment from left to right against 127.6533.72.Affected if The first number is less than 127, OR the first number equals 127 but the second number is less than 6533, OR the first two numbers match 127.6533 but the third number is less than 72
-
Check if Chrome is managed by your organizationIf Chrome is enterprise-managed, the version may be set by group policy. Verify with your IT or security team what version deployment they are using.Affected if Your organization has not yet deployed version 127.6533.72 or later through their endpoint management
You are affected if your Google Chrome installation shows a version number lower than 127.6533.72 on the About page.
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 · scoped127.0.6533.72
Update Google Chrome to version 127.0.6533.72 or later to patch the vulnerability. Organizations should deploy the browser update through their patch management systems.
Chrome 127.0.6533.72 or later
- Open Chrome and navigate to chrome://version to check your current version
- If the version is earlier than 127.0.6533.72, navigate to chrome://settings/help or click Help > About Google Chrome
- Chrome will automatically check for and install the latest version
- Restart Chrome after the update completes
- Verify the version is 127.0.6533.72 or later by checking chrome://version again
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-2024-6994 — 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-2024-6994 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