CVE-2026-53657

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to 2.1.3, on an instance of Lima running with the qemu driver, an arbitrary user in the VM could access /run/lima-guestagent.sock when the guest agent is enabled, which could result in running arbitrary commands with root privileges in the VM because the guest agent socket provides tunneling for arbitrary addresses, including Unix socket addresses for privileged daemons like D-Bus. This issue is fixed in version 2.1.3.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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 (value × EchelonGraph’s weight)
Severity82% × 45%
The EG Score, 8.2 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (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

Published

July 10, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

An arbitrary user in a QEMU VM could gain the root privilege in the VM via the guest agent socket · Advisory · lima-vm/lima · GitHub

https://github.com/lima-vm/lima/security/advisories/GHSA-2j9v-p4xj-cjw2
GitHub release Patch Available

v2.1.3

Patch available: lima-vm/lima v2.1.3

https://github.com/lima-vm/lima/releases/tag/v2.1.3
GitHub commit

commit b08cae8a670c (lima-vm/lima)

Fix landed in lima-vm/lima commit b08cae8a670c — awaiting tagged release

https://github.com/lima-vm/lima/commit/b08cae8a670cf916d5da11c48a6de76dabd89678
GitHub commit

commit 8a45892378d2 (lima-vm/lima)

Fix landed in lima-vm/lima commit 8a45892378d2 — awaiting tagged release

https://github.com/lima-vm/lima/commit/8a45892378d22f40505c31a38f786a07701b6d50

Vendor Advisories for CVE-2026-53657(1)

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

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/lima-vm/lima—
  • every version on: no fix on record
—
github.com/lima-vm/lima/v2—
  • every version up to 2.1.3: fixed in 2.1.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 33× 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 134 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 34 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/lima-vm/lima

Frequently asked(5)

What is CVE-2026-53657?
CVE-2026-53657 is a high-severity vulnerability; its CVE record was published on July 10, 2026. Lima launches Linux virtual machines, typically on macOS, for running containerd. Prior to 2.1.3, on an instance of Lima running with the qemu driver, an arbitrary user in the VM could access /run/lima-guestagent.sock when the guest agent is enabled, which could result in running arbitrary commands…
When was the CVE record for CVE-2026-53657 published?
The CVE record for CVE-2026-53657 was published on July 10, 2026. 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 July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-53657 actively exploited?
CVE-2026-53657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53657?
CVE-2026-53657 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53657?
A fix for CVE-2026-53657 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53657 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-2026-53657

Explore →

Is Your Infrastructure Affected by CVE-2026-53657?

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

Book a Demo →Browse All CVEs