CVE-2022-1096

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under NVD CVSS v3. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 25%CVSS: 8.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Type confusion in V8 in Google Chrome prior to 99.0.4844.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
80
EG Risk 80/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
25%
EPSS %ILE
97th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
25% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2022-1096

Published

July 23, 2022

Last Modified

October 24, 2025

Advisory Details (4)

Auto-updated Oct 19, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-1096
Web page

Chromium, Google Chrome, Microsoft Edge, QtWebEngine: Multiple Vulnerabilities (GLSA 202208-25) — Gentoo security

https://security.gentoo.org/glsa/202208-25
Web page

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_25.html

Vendor Advisories for CVE-2022-1096(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuchromium-browser (99.0.4844.84-0ubuntu0.18.04.1) @ bionic2026-10-22ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium90.0.4430.212-1 ... 99.0.4844.74-1~deb11u1 (17 versions)
  • every version up to 99.0.4844.84-1~deb11u1: fixed in 99.0.4844.84-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 99.0.4844.84-1: fixed in 99.0.4844.84-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 99.0.4844.84-1: fixed in 99.0.4844.84-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 99.0.4844.84-1: fixed in 99.0.4844.84-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 192× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,162 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,062 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  2. 2026-10-23 10:22 UTCEG score recompute
  3. 2026-10-23 10:22 UTCVendor advisory
  4. 2026-10-22 16:29 UTCEPSS rescoreEPSS 25% · 97th percentile
  5. 2026-10-22 12:02 UTCEG score recompute
  6. 2026-10-22 12:02 UTCVendor advisory
  7. 2026-10-21 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  8. 2026-10-21 13:43 UTCEG score recompute
  9. 2026-10-21 13:43 UTCVendor advisory
  10. 2026-10-20 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  11. 2026-10-20 15:24 UTCVendor advisory
  12. 2026-10-19 17:05 UTCEG score recompute
  13. 2026-10-19 17:05 UTCVendor advisory
  14. 2026-10-19 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  15. 2026-10-18 18:45 UTCEG score recompute
  16. 2026-10-18 18:45 UTCVendor advisory
  17. 2026-10-18 08:47 UTCEG score recompute
  18. 2026-10-17 20:26 UTCEG score recompute
  19. 2026-10-17 20:26 UTCVendor advisory
  20. 2026-10-17 16:29 UTCEPSS rescoreEPSS 25% · 97th percentile
  21. 2026-10-16 22:07 UTCEG score recompute
  22. 2026-10-16 22:07 UTCVendor advisory
  23. 2026-10-16 16:34 UTCEPSS rescoreEPSS 25% · 97th percentile
  24. 2026-10-15 23:49 UTCEG score recompute
  25. 2026-10-15 23:49 UTCVendor advisory
Show 75 more
  1. 2026-10-15 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  2. 2026-10-15 01:31 UTCEG score recompute
  3. 2026-10-14 16:29 UTCEPSS rescoreEPSS 25% · 97th percentile
  4. 2026-10-14 03:13 UTCEG score recompute
  5. 2026-10-14 03:13 UTCVendor advisory
  6. 2026-10-13 16:28 UTCEPSS rescoreEPSS 25% · 97th percentile
  7. 2026-10-13 04:54 UTCVendor advisory
  8. 2026-10-12 19:04 UTCEG score recompute
  9. 2026-10-12 06:34 UTCVendor advisory
  10. 2026-10-12 02:45 UTCVendor advisory
  11. 2026-10-11 23:00 UTCVendor advisory
  12. 2026-10-11 19:15 UTCEG score recompute
  13. 2026-10-11 19:15 UTCVendor advisory
  14. 2026-10-11 15:29 UTCEG score recompute
  15. 2026-10-11 15:29 UTCVendor advisory
  16. 2026-10-11 13:44 UTCEPSS rescoreEPSS 25% · 97th percentile
  17. 2026-10-11 11:43 UTCEG score recompute
  18. 2026-10-11 11:43 UTCVendor advisory
  19. 2026-10-11 07:56 UTCVendor advisory
  20. 2026-10-11 04:11 UTCVendor advisory
  21. 2026-10-11 00:25 UTCVendor advisory
  22. 2026-10-10 20:38 UTCEG score recompute
  23. 2026-10-10 20:38 UTCVendor advisory
  24. 2026-10-10 19:56 UTCEPSS rescoreEPSS 25% · 97th percentile
  25. 2026-10-10 13:03 UTCVendor advisory
  26. 2026-10-10 09:18 UTCVendor advisory
  27. 2026-10-10 05:33 UTCVendor advisory
  28. 2026-10-10 01:48 UTCVendor advisory
  29. 2026-10-09 22:03 UTCEG score recompute
  30. 2026-10-09 22:03 UTCVendor advisory
  31. 2026-10-09 20:04 UTCEPSS rescoreEPSS 25% · 97th percentile
  32. 2026-10-09 18:17 UTCVendor advisory
  33. 2026-10-09 14:32 UTCVendor advisory
  34. 2026-10-09 10:42 UTCVendor advisory
  35. 2026-10-09 06:51 UTCVendor advisory
  36. 2026-10-09 03:06 UTCVendor advisory
  37. 2026-10-08 23:20 UTCVendor advisory
  38. 2026-10-08 19:35 UTCEG score recompute
  39. 2026-10-08 19:35 UTCVendor advisory
  40. 2026-10-08 16:40 UTCEPSS rescoreEPSS 25% · 97th percentile
  41. 2026-10-08 15:49 UTCVendor advisory
  42. 2026-10-08 12:04 UTCVendor advisory
  43. 2026-10-08 08:18 UTCVendor advisory
  44. 2026-10-08 04:33 UTCVendor advisory
  45. 2026-10-08 00:47 UTCEG score recompute
  46. 2026-10-08 00:47 UTCVendor advisory
  47. 2026-10-07 23:45 UTCEPSS rescoreEPSS 24% · 97th percentile
  48. 2026-10-07 21:01 UTCVendor advisory
  49. 2026-10-07 17:16 UTCVendor advisory
  50. 2026-10-07 13:30 UTCVendor advisory
  51. 2026-10-07 09:44 UTCVendor advisory
  52. 2026-10-07 05:58 UTCVendor advisory
  53. 2026-10-07 02:13 UTCVendor advisory
  54. 2026-10-06 22:28 UTCVendor advisory
  55. 2026-10-06 18:43 UTCEG score recompute
  56. 2026-10-06 18:43 UTCVendor advisory
  57. 2026-10-06 15:14 UTCEPSS rescoreEPSS 24% · 97th percentile
  58. 2026-10-06 14:58 UTCVendor advisory
  59. 2026-10-06 11:13 UTCVendor advisory
  60. 2026-10-06 07:28 UTCVendor advisory
  61. 2026-10-06 03:43 UTCVendor advisory
  62. 2026-10-05 23:57 UTCVendor advisory
  63. 2026-10-05 20:13 UTCEG score recompute
  64. 2026-10-05 20:13 UTCVendor advisory
  65. 2026-10-05 17:40 UTCEPSS rescoreEPSS 24% · 97th percentile
  66. 2026-10-05 16:27 UTCVendor advisory
  67. 2026-10-05 12:42 UTCVendor advisory
  68. 2026-10-05 08:57 UTCVendor advisory
  69. 2026-10-05 05:12 UTCVendor advisory
  70. 2026-10-05 01:27 UTCVendor advisory
  71. 2026-10-04 21:42 UTCVendor advisory
  72. 2026-10-04 17:57 UTCVendor advisory
  73. 2026-10-04 14:08 UTCVendor advisory
  74. 2026-10-04 10:21 UTCVendor advisory
  75. 2026-10-04 06:35 UTCVendor advisory

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCMav3r1ck0x1/Chrome-and-Edge-Version-Dumper
    Published Mar 29, 2022

    Powershell script that dumps Chrome and Edge version to a text file in order to determine if you need to update due to CVE-2022-1096

    Open source ↗

Frequently asked(6)

What is CVE-2022-1096?
CVE-2022-1096 is a critical-severity vulnerability; its CVE record was published on July 23, 2022. Type confusion in V8 in Google Chrome prior to 99.0.4844.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
When was the CVE record for CVE-2022-1096 published?
The CVE record for CVE-2022-1096 was published on July 23, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2025; the record at its source may have been updated since.
Is CVE-2022-1096 actively exploited?
Yes. CISA added CVE-2022-1096 to the Known Exploited Vulnerabilities catalog on March 28, 2022, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2022-1096?
CVE-2022-1096 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2022-1096?
CVE-2022-1096 affects Google Chromium V8. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2022-1096?
A fix for CVE-2022-1096 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-1096 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-1096

Explore →

Is Your Infrastructure Affected by CVE-2022-1096?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.