CVE-2026-15310

LOWPre-NVD 2.12.1
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd 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 — 4 sources updated this week
2.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 2.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When decompressing crafted zip files using the bzip/LZMA/Zstandard

compressions, Python could use an attacker-controlled size to

pre-allocate memory, possibly resulting in memory exhaustion.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
10
EG Risk 10/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)
Severity21% × 45%
The EG Score, 2.1 of 10.
Exploitation0.5% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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)60 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 partial (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

August 25, 2026

Last Modified

October 2, 2026

References (13)

Vendor Advisories for CVE-2026-15310(2)

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

Affected Packages

(9 across 7 ecosystems)
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
python3.133.13.11-1 ... 3.13.9-1 (9 versions)
  • every version on: no fix on record
—
python3.143.14.0-1 ... 3.14.7-2 (26 versions)
  • every version up to 3.14.7-3: fixed in 3.14.7-3
—
python3.153.15.0~a8-1 ... 3.15.0~rc1-1 (9 versions)
  • every version up to 3.15.0~rc2-1: fixed in 3.15.0~rc2-1
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.14.8-r0: fixed in 3.14.8-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python3.113.11.2-6 ... 3.11.2-6+deb12u8 (9 versions)
  • every version up to 3.11.2-6+deb12u9: fixed in 3.11.2-6+deb12u9
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python3.133.13.11-1 ... 3.13.9-1 (14 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-15310?
CVE-2026-15310 is a low-severity vulnerability; its CVE record was published on August 25, 2026. When decompressing crafted zip files using the bzip/LZMA/Zstandard compressions, Python could use an attacker-controlled size to pre-allocate memory, possibly resulting in memory exhaustion.
When was the CVE record for CVE-2026-15310 published?
The CVE record for CVE-2026-15310 was published on August 25, 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 October 2, 2026; the record at its source may have been updated since.
Is CVE-2026-15310 actively exploited?
CVE-2026-15310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15310?
CVE-2026-15310 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15310?
A fix for CVE-2026-15310 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15310 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-15310

Explore →

Is Your Infrastructure Affected by CVE-2026-15310?

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

Book a Demo →Browse All CVEs