CVE-2023-44392

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.8% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

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

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Garden provides automation for Kubernetes development and testing. Prior tov ersions 0.13.17 and 0.12.65, Garden has a dependency on the cryo library, which is vulnerable to code injection due to an insecure implementation of deserialization. Garden stores serialized objects using cryo in the Kubernetes ConfigMap resources prefixed with test-result and run-result to cache Garden test and run results. These ConfigMaps are stored either in the garden-system namespace or the configured user namespace. When a user invokes the command garden test or garden run objects stored in the ConfigMap are retrieved and deserialized. This can be used by an attacker with access to the Kubernetes cluster to store malicious objects in the ConfigMap, which can trigger a remote code execution on the users machine when cryo deserializes the object. In order to exploit this vulnerability, an attacker must have access to the Kubernetes cluster used to deploy garden remote environments. Further, a user must actively invoke either a garden test or garden run which has previously cached results. The issue has been patched in Garden versions 0.13.17 (Bonsai) and 0.12.65 (Acorn). Only Garden versions prior to these are vulnerable. No known workarounds are available.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

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 its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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

October 9, 2023

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Arbitrary code execution vulnerability when using shared Kubernetes cluster · Advisory · garden-io/garden · GitHub

https://github.com/garden-io/garden/security/advisories/GHSA-hm75-6vc9-8rpr
GitHub commit

commit 3117964da40d (garden-io/garden)

Fix landed in garden-io/garden commit 3117964da40d — awaiting tagged release

https://github.com/garden-io/garden/commit/3117964da40d3114f129a6131b4ada89eaa4eb8c

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 36× 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 86 of 206 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. 14 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 00:48 UTCEG score recompute
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  3. 2026-10-21 23:54 UTCEG score recompute
  4. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-10-20 23:02 UTCEG score recompute
  6. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-18 07:49 UTCEG score recompute
  10. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  15. 2026-10-12 22:24 UTCOSV refresh
  16. 2026-10-12 18:18 UTCEG score recompute
  17. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-10-11 21:44 UTCEG score recompute
  19. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 61 more
  1. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-09-30 16:31 UTCEG score recompute
  5. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-09-26 15:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-09-22 20:31 UTCOSV refresh
  14. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-09-18 19:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  26. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  27. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  28. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  29. 2026-09-03 16:16 UTCOSV refresh
  30. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  34. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  35. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  36. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  37. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  38. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  39. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  40. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  41. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  42. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  43. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-08-17 05:50 UTCOSV refresh
  45. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  47. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  49. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  50. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  51. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  52. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  53. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  54. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  55. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  56. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  57. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  58. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  59. 2026-08-02 00:06 UTCOSV refresh
  60. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  61. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-44392?
CVE-2023-44392 is a critical-severity vulnerability; its CVE record was published on October 9, 2023. Garden provides automation for Kubernetes development and testing. Prior tov ersions 0.13.17 and 0.12.65, Garden has a dependency on the cryo library, which is vulnerable to code injection due to an insecure implementation of deserialization. Garden stores serialized objects using cryo in the…
When was the CVE record for CVE-2023-44392 published?
The CVE record for CVE-2023-44392 was published on October 9, 2023. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-44392 actively exploited?
CVE-2023-44392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-44392?
CVE-2023-44392 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2023-44392?
A fix for CVE-2023-44392 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-44392?

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

Book a Demo →Browse All CVEs