CVE-2023-32684

LOWNVD 2.72.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.7 under NVD CVSS v3. EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 2.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to version 0.16.0, a virtual machine instance with a malicious disk image could read a single file on the host filesystem, even when no filesystem is mounted from the host. The official templates of Lima and the well-known third party products (Colima, Rancher Desktop, and Finch) are unlikely to be affected by this issue. To exploit this issue, the attacker has to embed the target file path (an absolute or a relative path from the instance directory) in a malicious disk image, as the qcow2 (or vmdk) backing file path string. As Lima refuses to run as the root, it is practically impossible for the attacker to read the entire host disk via /dev/rdiskN. Also, practically, the attacker cannot read at least the first 512 bytes (MBR) of the target file. The issue has been patched in Lima in version 0.16.0 by prohibiting using a backing file path in the VM base image.

CVSS v3
2.7
EG Score
2.7LOWmedium confidence
EG Risk
12
EG Risk 12/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
Severity27% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

May 30, 2023

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/lima-vm/lima—
  • every version up to 0.16.0: fixed in 0.16.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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 190 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-32684?
CVE-2023-32684 is a low vulnerability published on May 30, 2023. Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to version 0.16.0, a virtual machine instance with a malicious disk image could read a single file on the host filesystem, even when no filesystem is mounted from the host. The official templates of Lima and the…
When was CVE-2023-32684 disclosed?
CVE-2023-32684 was first published on May 30, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-32684 actively exploited?
CVE-2023-32684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-32684?
CVE-2023-32684 has a CVSS v3 base score of 2.7 (NVD).
How do I remediate CVE-2023-32684?
A fix for CVE-2023-32684 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-32684

Explore →

Is Your Infrastructure Affected by CVE-2023-32684?

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