CVE-2026-53940

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th 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
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-83974 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Conda is a system-level binary package and environment manager that runs on major operating systems and platforms. Prior to 26.5.2, parse_entry_point_def in conda/common/path/python.py accepted an unvalidated entry-point command from a noarch:python package's info/link.json metadata. CreatePythonEntryPointAction in conda/core/path_actions.py interpolated that command into target_short_path, and PrefixPathAction.target_full_path joined it to the installation prefix without verifying that the result remained under the intended bin or Scripts directory. create_python_entry_point in conda/gateways/disk/create.py then wrote an executable wrapper to the resulting path. A malicious package could use path separators, traversal segments, or an absolute command path to write outside the prefix or overwrite another in-prefix entry point during default install and environment transactions. Out-of-prefix writes require the target parent directory to exist, while an overwritten entry point can execute attacker-controlled Python when later invoked with the installing user's privileges. This issue is fixed in version 26.5.2.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

26.5.2

Patch available: conda/conda 26.5.2

https://github.com/conda/conda/releases/tag/26.5.2
GitHub commit

commit 3987c86ccd55 (conda/conda)

Fix landed in conda/conda commit 3987c86ccd55 — awaiting tagged release

https://github.com/conda/conda/commit/3987c86ccd5527177e96b48bd4dc1777dd2c9baa
GitHub pull request

Backport fix for a 26.5.x patch release

Fix merged in conda/conda PR #16168 on 2026-06-01 — awaiting tagged release

https://github.com/conda/conda/pull/16168
GitHub advisoryMentions a patch (unverified)

Entry-point path traversal in noarch:python install (arbitrary file write) — canonical Python implementation · Advisory · conda/conda · GitHub

https://github.com/conda/conda/security/advisories/GHSA-9m8m-c4j3-rj2c

Vendor Advisories for CVE-2026-53940(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53940?
CVE-2026-53940 is a high-severity vulnerability; its CVE record was published on September 21, 2026. Conda is a system-level binary package and environment manager that runs on major operating systems and platforms. Prior to 26.5.2, parse_entry_point_def in conda/common/path/python.py accepted an unvalidated entry-point command from a noarch:python package's info/link.json metadata.…
When was the CVE record for CVE-2026-53940 published?
The CVE record for CVE-2026-53940 was published on September 21, 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 September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-53940 actively exploited?
CVE-2026-53940 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53940?
CVE-2026-53940 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53940?
A fix for CVE-2026-53940 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53940 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53940

Explore →

Is Your Infrastructure Affected by CVE-2026-53940?

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

Book a Demo →Browse All CVEs