CVE-2026-31958

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Tornado is a Python web framework and asynchronous networking library. In versions of Tornado prior to 6.5.5, the only limit on the number of parts in multipart/form-data is the max_body_size setting (default 100MB). Since parsing occurs synchronously on the main thread, this creates the possibility of denial-of-service due to the cost of parsing very large multipart bodies with many parts. This vulnerability is fixed in 6.5.5.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

March 12, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
Patch available. Sources: github.
generic Patch Available

[SECURITY] [DLA 4520-1] python-tornado security update

https://lists.debian.org/debian-lts-announce/2026/04/msg00000.html
github Patch Available

DoS due to too many multipart parts · Advisory · tornadoweb/tornado · GitHub

https://github.com/tornadoweb/tornado/security/advisories/GHSA-qjxf-f2mg-c6mc

Vendor Advisories for CVE-2026-31958(18)

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

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17824716972026-07-09redhat
ubuntupython3-tornado (6.0.3+really5.1.1-3ubuntu0.1~esm5) @ focal2026-06-12ubuntu
ubuntupython3-tornado (6.5.4-0.1ubuntu0.1) @ resolute2026-06-12ubuntu
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17800692222026-06-10redhat
redhatpython-tornado-0:4.2.1-5.el7_9.32026-06-08redhat
redhatpython-tornado-0:6.4.2-1.el9_4.22026-05-26redhat
redhatpython-tornado-0:6.4.2-1.el9_2.22026-05-26redhat
redhatpython-tornado-0:6.4.2-2.el9_6.32026-05-26redhat
redhatpython-tornado-0:6.4.2-1.el10_0.22026-05-26redhat
redhatpython-tornado-0:6.5.5-1.el10_22026-05-19redhat
redhatpython-tornado-0:6.5.5-1.el9_82026-05-19redhat
redhatpython-tornado-0:6.5.5-1.el9_7.12026-05-05redhat
redhatpython-tornado-0:6.5.5-1.el10_1.12026-05-05redhat
redhatpcs-0:0.11.1-10.el9_0.112026-04-29redhat
redhatpcs-0:0.10.8-1.el8_4.112026-04-29redhat
redhatpcs-0:0.10.12-6.el8_6.132026-04-29redhat
redhatpcs-0:0.10.15-4.el8_8.112026-04-29redhat
redhatrhoai/odh-llama-stack-core-rhel9:17751444032026-04-23redhat
redhatpcs-0:0.10.18-2.el8_10.92026-04-14redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.1.0-1, 6.1.0-1+deb11u1, 6.1.0-1+deb11u2, 6.1.0-1+deb11u36.1.0-1+deb11u4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.2.0-3 ... 6.5.5-4 (23 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.4.2-3 ... 6.5.5-4 (12 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.4.2-3 ... 6.5.4-1 (6 versions)6.5.5-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
tornado0.2 ... 6.5b1 (80 versions)6.5.5—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-31958?
CVE-2026-31958 is a high vulnerability published on March 12, 2026. Tornado is a Python web framework and asynchronous networking library. In versions of Tornado prior to 6.5.5, the only limit on the number of parts in multipart/form-data is the maxbodysize setting (default 100MB). Since parsing occurs synchronously on the main thread, this creates the possibility…
When was CVE-2026-31958 disclosed?
CVE-2026-31958 was first published in the National Vulnerability Database on March 12, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31958 actively exploited?
CVE-2026-31958 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31958?
CVE-2026-31958 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31958?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31958, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31958

Explore →

Is Your Infrastructure Affected by CVE-2026-31958?

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

Start Free Scan →Browse All CVEs