CVE-2026-39803

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% 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
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows unauthenticated remote denial of service via memory exhaustion.

The chunked clause of 'Elixir.Bandit.HTTP1.Socket':read_data/2 in lib/bandit/http1/socket.ex ignores the caller-supplied :length option when reading HTTP/1 chunked request bodies. Instead of capping the accumulated body at the configured limit (e.g. Plug.Parsers' default 8 MB), do_read_chunked_data!/5 buffers every received chunk into an iolist unconditionally and materializes the entire body as a single binary. The function always returns {:ok, body, ...}, so callers cannot interpose a 413 response.

Because Plug.Parsers runs before routing and authentication in the standard Phoenix endpoint, an unauthenticated attacker needs no valid route or credentials. Sending a single Transfer-Encoding: chunked POST request with an arbitrarily large body to any path causes the BEAM process to exhaust available memory and be terminated by the OS OOM killer.

The content-length path in the same function correctly enforces the limit and is not affected.

This issue affects bandit: from 1.4.0 before 1.11.1.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
46.5%
KEV
Not listed

Published

May 13, 2026

Last Modified

May 21, 2026

Advisory Details (4)

Auto-updated May 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unauthenticated one-shot DoS via `Transfer-Encoding: chunked` · Advisory · mtrudel/bandit · GitHub

https://github.com/mtrudel/bandit/security/advisories/GHSA-9q9q-324x-93r2
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-39803
generic

Improve chunk handling (#585) · mtrudel/bandit@ae3520d · GitHub

https://github.com/mtrudel/bandit/commit/ae3520dfdbfab115c638f8c7f6f6b805db34e1ab
generic

HTTP/1 chunked body reader ignores length cap in bandit | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-39803.html

Vendor Advisories for CVE-2026-39803(1)

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

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
bandit1.10.0 ... 1.9.0 (32 versions)1.11.1

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-39803?
CVE-2026-39803 is a high vulnerability published on May 13, 2026. Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows unauthenticated remote denial of service via memory exhaustion. The chunked clause of 'Elixir.Bandit.HTTP1.Socket':readdata/2 in lib/bandit/http1/socket.ex ignores the caller-supplied :length option when…
When was CVE-2026-39803 disclosed?
CVE-2026-39803 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39803 actively exploited?
CVE-2026-39803 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-39803?
CVE-2026-39803 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-39803?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39803, 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-39803

Explore →

Is Your Infrastructure Affected by CVE-2026-39803?

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