CVE-2024-0812

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2024-01-24. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Inappropriate implementation in Accessibility in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: High)

CVSS v3
8.8
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 24, 2024

Last Modified

May 30, 2025

Advisory Details (4)

Auto-updated Aug 30, 2026
No patch confirmed yet.
generic

[SECURITY] Fedora 38 Update: chromium-121.0.6167.85-1.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/VXDSGAFQD4BDB4IB2O4ZUSHC3JCVQEKC/
generic

[SECURITY] Fedora 39 Update: chromium-121.0.6167.85-1.fc39 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/MMI6GXFONZV6HE3BPZO3AP6GUVQLG4JQ/
generic
https://crbug.com/1484394
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html

Vendor Advisories for CVE-2024-0812(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 120.0.6099.71-1~deb12u1 (85 versions)121.0.6167.85-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium—121.0.6167.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium—121.0.6167.85-1—

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 173 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-0812?
CVE-2024-0812 is a high vulnerability published on January 24, 2024. Inappropriate implementation in Accessibility in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: High)
When was CVE-2024-0812 disclosed?
CVE-2024-0812 was first published on January 24, 2024, with the most recent update on May 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-0812 actively exploited?
CVE-2024-0812 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-0812?
CVE-2024-0812 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-0812?
No fix for CVE-2024-0812 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2024-0812 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-2024-0812

Explore →

Is Your Infrastructure Affected by CVE-2024-0812?

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

Book a Demo →Browse All CVEs