ChromeWeb browser · Google
CVE-2022-1364
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 · uneditedType confusion in V8 Turbofan in Google Chrome prior to 100.0.4896.127 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 confidenceType confusion vulnerability in Google Chrome's V8 Turbofan JavaScript JIT compiler. A remote attacker can exploit this by tricking users into visiting a crafted malicious HTML page, potentially leading to heap corruption and arbitrary code execution.
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
< 100.0.4896.127CVSS 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 Google Chrome, click the three-dot menu in the top right, select Help, then select About Google Chrome. The version number is displayed on this page.Affected if The displayed version is less than 100.0.4896.127 (for example, 100.0.4896.75 or any earlier version).
-
Verify V8 JavaScript engine is enabledThis check is implicit. The V8 engine is always enabled in standard Google Chrome installations and cannot be disabled through user settings. The vulnerability exists in the V8 Turbofan JIT compiler component.Affected if V8 is enabled (which is the default and cannot be changed in regular Chrome usage).
-
Confirm browser is not using Chromium Edge or another Chromium-based browserEnsure the browser being checked is specifically Google Chrome, not Microsoft Edge, Brave, or other Chromium-based browsers, as this CVE applies only to Google Chrome.Affected if The browser is Google Chrome with a version prior to 100.0.4896.127.
If Google Chrome version is less than 100.0.4896.127, the environment is affected by this vulnerability.
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 · scoped100.0.4896.127
Update Google Chrome to version 100.0.4896.127 or later. Organizations should deploy the browser update via standard patch management processes.
Chrome 100.0.4896.127 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version and allow Chrome to check for updates
- If version is below 100.0.4896.127, click 'Update Google Chrome' to install the latest version
- Restart the browser after the update completes
- Alternatively, download the latest stable Chrome version from the official Google Chrome website (chrome.com) and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1364 — 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-2022-1364 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