CVE-2026-41140

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. 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, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Poetry is a dependency manager for Python. Prior to 2.3.4, the extractall() function in src/poetry/utils/helpers.py:410-426 extracts sdist tarballs without path traversal protection on Python versions where tarfile.data_filter is unavailable. Considering only Python versions which are still supported by Poetry, these are 3.10.0 - 3.10.12 and 3.11.0 - 3.11.4. This vulnerability is fixed in 2.3.4.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

Published

April 24, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
Patch available. Sources: github, redhat.
redhat

2461604 – (CVE-2026-41140) CVE-2026-41140 poetry: Poetry: Path traversal vulnerability allows arbitrary file write via malicious package extraction

https://bugzilla.redhat.com/show_bug.cgi?id=2461604
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-41140
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:24866
githubMentions a patch (unverified)

Path traversal in tar extraction on Python 3.10.0 - 3.10.12 and 3.11.0 - 3.11.4 · Advisory · python-poetry/poetry · GitHub

https://github.com/python-poetry/poetry/security/advisories/GHSA-73h3-mf4w-8647

Vendor Advisories for CVE-2026-41140(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17801027322026-06-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
poetry1.3.2+dfsg-3 ... 2.3.4-2 (31 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
poetry—
  • every version up to 2.1.2+dfsg-1: fixed in 2.1.2+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
poetry—
  • every version up to 2.1.2+dfsg-1: fixed in 2.1.2+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
poetry0.1.0 ... 2.3.3 (184 versions)
  • every version up to 2.3.4: fixed in 2.3.4
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-41140?
CVE-2026-41140 is a high vulnerability published on April 24, 2026. Poetry is a dependency manager for Python. Prior to 2.3.4, the extractall() function in src/poetry/utils/helpers.py:410-426 extracts sdist tarballs without path traversal protection on Python versions where tarfile.data_filter is unavailable. Considering only Python versions which are still…
When was CVE-2026-41140 disclosed?
CVE-2026-41140 was first published on April 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41140 actively exploited?
CVE-2026-41140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41140?
CVE-2026-41140 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-41140?
A fix for CVE-2026-41140 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41140 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-41140

Explore →

Is Your Infrastructure Affected by CVE-2026-41140?

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