CVE-2023-33119

HIGHNVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2024-05-06. NVD baseline CVSS 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: NoneExposed: 0

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

Memory corruption while loading a VM from a signed VM image that is not coherent in the processor cache.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.2%
KEV
Not listed

Published

May 6, 2024

Last Modified

August 11, 2025

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 18× 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.

  1. 2026-07-23 02:23 UTCEG score recompute
  2. 2026-07-22 23:10 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-18 10:03 UTCEPSS rescore
  5. 2026-07-18 10:03 UTCEPSS rescore
  6. 2026-07-16 17:01 UTCEPSS rescore
  7. 2026-07-13 06:11 UTCEPSS rescore
  8. 2026-07-13 06:11 UTCEPSS rescore
  9. 2026-07-09 19:08 UTCEPSS rescore
  10. 2026-07-09 19:08 UTCEPSS rescore
  11. 2026-07-08 15:13 UTCEPSS rescore
  12. 2026-07-07 13:44 UTCEPSS rescore
  13. 2026-07-06 02:21 UTCEPSS rescore
  14. 2026-07-02 16:59 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-18 17:51 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-17 17:51 UTCEPSS rescore
  24. 2026-06-17 17:51 UTCEPSS rescore
  25. 2026-06-16 17:51 UTCEPSS rescore
Show 46 more
  1. 2026-06-16 17:51 UTCEPSS rescore
  2. 2026-06-15 17:47 UTCEPSS rescore
  3. 2026-06-14 23:16 UTCEPSS rescore
  4. 2026-06-13 22:59 UTCEPSS rescore
  5. 2026-06-13 22:59 UTCEPSS rescore
  6. 2026-06-12 23:10 UTCEPSS rescore
  7. 2026-06-12 23:10 UTCEPSS rescore
  8. 2026-06-11 13:59 UTCEPSS rescore
  9. 2026-06-11 13:59 UTCEPSS rescore
  10. 2026-06-10 22:17 UTCEPSS rescore
  11. 2026-06-10 13:21 UTCEPSS rescore
  12. 2026-06-08 14:16 UTCEPSS rescore
  13. 2026-06-08 14:15 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-07 15:23 UTCEPSS rescore
  16. 2026-06-06 13:46 UTCEPSS rescore
  17. 2026-06-06 13:46 UTCEPSS rescore
  18. 2026-06-05 22:46 UTCEPSS rescore
  19. 2026-06-05 22:46 UTCEPSS rescore
  20. 2026-06-05 06:09 UTCEPSS rescore
  21. 2026-06-05 06:09 UTCEPSS rescore
  22. 2026-06-04 13:11 UTCEPSS rescore
  23. 2026-06-04 13:11 UTCEPSS rescore
  24. 2026-06-02 20:12 UTCEPSS rescore
  25. 2026-06-02 20:12 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-05-31 22:30 UTCEPSS rescore
  30. 2026-05-31 22:29 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 00:15 UTCEPSS rescore
  33. 2026-05-31 00:15 UTCEPSS rescore
  34. 2026-05-29 13:43 UTCEPSS rescore
  35. 2026-05-29 13:43 UTCEPSS rescore
  36. 2026-05-28 13:43 UTCEPSS rescore
  37. 2026-05-28 13:43 UTCEPSS rescore
  38. 2026-05-27 13:39 UTCEPSS rescore
  39. 2026-05-26 13:43 UTCEPSS rescore
  40. 2026-05-26 13:43 UTCEPSS rescore
  41. 2026-05-26 07:18 UTCEPSS rescore
  42. 2026-05-26 07:18 UTCEPSS rescore
  43. 2026-05-26 07:18 UTCEPSS rescore
  44. 2026-05-24 16:52 UTCEPSS rescore
  45. 2026-05-24 02:51 UTCEG score recompute
  46. 2026-05-24 02:51 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2023-33119?
CVE-2023-33119 is a high vulnerability published on May 6, 2024. Memory corruption while loading a VM from a signed VM image that is not coherent in the processor cache.
When was CVE-2023-33119 disclosed?
CVE-2023-33119 was first published in the National Vulnerability Database on May 6, 2024, with the most recent update on August 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-33119 actively exploited?
CVE-2023-33119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-33119?
CVE-2023-33119 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2023-33119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-33119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-33119

Explore →

Is Your Infrastructure Affected by CVE-2023-33119?

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

Start Free Scan →Browse All CVEs