Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
CISA KEV · ACTIVELY EXPLOITED
HIGH severity

CVE-2022-1364 — Chrome

HIGH

CVE-2022-1364 is a high-severity (CVSS 8.8) CWE-843 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-04-15) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published
Updated
Affected
1 product
Patched
See advisory
Exploits
6 known
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-04-15. Federal agencies were required to remediate by 2022-05-06.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-1364.

EPSS Exploitation Probability

via FIRST.org ↗
13.9%probability of exploitation in next 30 days
Moderate Risk+0.20%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
10.9%13.6%16.3%19.0%12.4%13.9%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-1364 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Type 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.

Affected Products

1 product · 1 configurations
Application
chromegoogle
< 100.0.4896.127
range
Exploits & PoCs
6

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    No fixed release is recorded for CVE-2022-1364 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Type 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.
O3 Security · Impact-Aware SCA

Is CVE-2022-1364 in your dependencies?

Find it across , including transitive dependencies.

Actively Exploited: CVE-2022-1364: Chrome (High 8.8)