CVE-2026-38969

✕ Withdrawn — historical dataHIGHPre-NVD 7.5Elevated
7.5CVSS
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

ruby webrick through v1.9.2 WEBrick reparses trailer Content-Length into canonical request state, enabling request smuggling. NOTE: the Supplier reports that "The project README states that it is suitable for testing and development, and that its developers do not encourage its use to serve production web applications that may be subject to hostile input. It is not a production web server and is not intended to receive traffic from untrusted sources. Request smuggling is only reachable when WEBrick sits behind a proxy and receives hostile traffic in a production deployment, which is the configuration the project documents as discouraged."

CVSS v3
7.5
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

Published

July 2, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 6, 2026
Patch available. Sources: github_pr.
generic

[BUG] WEBrick reparses trailer Content-Length into canonical request state, enabling request metadata confusion / request smuggling · Issue #198 · ruby/webrick · GitHub

https://github.com/ruby/webrick/issues/198
github_pr

Only allow specific trailers

Upstream fix in progress (PR #199 · ruby/webrick, state=open)

https://github.com/ruby/webrick/pull/199

Vendor Advisories for CVE-2026-38969(3)

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
redhatrust-main-1.96.1-1.hum12026-07-02redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 0× in last 7d / 8× 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.

  1. 2026-09-23 06:37 UTCVendor advisory
  2. 2026-09-23 06:37 UTCGHSA enrichment
  3. 2026-09-18 06:14 UTCVendor advisory
  4. 2026-09-18 06:14 UTCGHSA enrichment
  5. 2026-09-12 14:14 UTCVendor advisory
  6. 2026-09-12 14:14 UTCGHSA enrichment
  7. 2026-09-05 23:51 UTCVendor advisory
  8. 2026-09-05 23:51 UTCGHSA enrichment
  9. 2026-08-30 11:21 UTCVendor advisory
  10. 2026-08-30 11:21 UTCGHSA enrichment
  11. 2026-08-25 13:40 UTCVendor advisory
  12. 2026-08-25 13:40 UTCGHSA enrichment
  13. 2026-08-22 06:05 UTCVendor advisory
  14. 2026-08-22 06:05 UTCGHSA enrichment
  15. 2026-08-18 20:54 UTCVendor advisory
  16. 2026-08-18 20:54 UTCGHSA enrichment
  17. 2026-08-15 07:56 UTCVendor advisory
  18. 2026-08-15 07:56 UTCGHSA enrichment
  19. 2026-08-12 00:24 UTCVendor advisory
  20. 2026-08-12 00:24 UTCGHSA enrichment
  21. 2026-08-08 17:59 UTCVendor advisory
  22. 2026-08-08 17:59 UTCGHSA enrichment
  23. 2026-08-05 11:39 UTCGHSA enrichment
  24. 2026-08-02 04:04 UTCEG score recompute
  25. 2026-08-02 04:04 UTCGHSA enrichment
Show 51 more
  1. 2026-07-29 21:42 UTCGHSA enrichment
  2. 2026-07-26 13:00 UTCEG score recompute
  3. 2026-07-26 13:00 UTCGHSA enrichment
  4. 2026-07-23 03:10 UTCEG score recompute▼ 7.50
  5. 2026-07-16 20:49 UTCGHSA enrichment
  6. 2026-07-16 08:07 UTCGHSA enrichment
  7. 2026-07-15 19:24 UTCGHSA enrichment
  8. 2026-07-15 06:42 UTCGHSA enrichment
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-14 17:59 UTCVendor advisory
  11. 2026-07-14 17:59 UTCGHSA enrichment
  12. 2026-07-14 05:18 UTCVendor advisory
  13. 2026-07-14 05:18 UTCGHSA enrichment
  14. 2026-07-13 22:30 UTCEPSS rescore
  15. 2026-07-13 16:35 UTCVendor advisory
  16. 2026-07-13 16:35 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 03:51 UTCVendor advisory
  20. 2026-07-13 03:51 UTCGHSA enrichment
  21. 2026-07-12 15:09 UTCVendor advisory
  22. 2026-07-12 15:08 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 02:24 UTCVendor advisory
  25. 2026-07-12 02:24 UTCGHSA enrichment
  26. 2026-07-11 13:42 UTCVendor advisory
  27. 2026-07-11 13:42 UTCGHSA enrichment
  28. 2026-07-11 08:27 UTCEPSS rescore
  29. 2026-07-11 01:00 UTCVendor advisory
  30. 2026-07-11 00:59 UTCGHSA enrichment
  31. 2026-07-10 12:17 UTCVendor advisory
  32. 2026-07-10 12:17 UTCGHSA enrichment
  33. 2026-07-09 23:33 UTCVendor advisory
  34. 2026-07-09 23:33 UTCGHSA enrichment
  35. 2026-07-09 19:10 UTCEPSS rescore
  36. 2026-07-09 10:50 UTCEG score recompute▲ 7.50
  37. 2026-07-09 10:50 UTCVendor advisory
  38. 2026-07-09 10:50 UTCGHSA enrichment
  39. 2026-07-08 15:15 UTCEPSS rescore
  40. 2026-07-07 13:46 UTCEPSS rescore
  41. 2026-07-06 16:27 UTCEPSS rescore
  42. 2026-07-06 16:27 UTCEPSS rescore
  43. 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  44. 2026-07-06 04:27 UTCVendor advisory
  45. 2026-07-06 04:27 UTCGHSA enrichment
  46. 2026-07-06 02:23 UTCEPSS rescore
  47. 2026-07-06 02:23 UTCEPSS rescore
  48. 2026-07-05 02:30 UTCEPSS rescore
  49. 2026-07-04 06:31 UTCEPSS rescore
  50. 2026-07-02 22:06 UTCEG score recompute
  51. 2026-07-02 22:06 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-38969?
CVE-2026-38969 is a high vulnerability published on July 2, 2026. ruby webrick through v1.9.2 WEBrick reparses trailer Content-Length into canonical request state, enabling request smuggling. NOTE: the Supplier reports that "The project README states that it is suitable for testing and development, and that its developers do not encourage its use to serve…
When was CVE-2026-38969 disclosed?
CVE-2026-38969 was first published on July 2, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-38969 actively exploited?
CVE-2026-38969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-38969?
CVE-2026-38969 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-38969?
A fix for CVE-2026-38969 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-38969 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-38969?

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

Book a Demo →Browse All CVEs