CVE-2026-48596

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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
Elevated
2.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.1Exploit: NoneExposed: 0

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

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in elixir-tesla tesla allows HTTP header injection via Tesla.Multipart.add_content_type_param/2.

Tesla.Multipart.add_content_type_param/2 appends caller-supplied strings to the multipart content_type_params list without validating for CR (\r) or LF (\n) characters. Tesla.Multipart.headers/1 then joins these params verbatim with "; " to construct the outgoing Content-Type header value. A param containing \r\n splits the header line, allowing arbitrary headers to be injected into the outbound HTTP request. Any application that forwards untrusted input (such as a user-supplied charset or parameter string) into add_content_type_param/2 is affected.

This issue affects tesla: from 0.8.0 before 1.18.3.

CVSS v3
2.1
EG Score
2.1(medium)
EPSS
6.7%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

References (5)

Vendor Advisories for CVE-2026-48596(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
tesla0.10.0 ... 1.9.0 (52 versions)1.18.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 31× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 40 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-24 14:05 UTCEPSS rescore
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-23 21:33 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-19 19:26 UTCEPSS rescore
  14. 2026-06-19 19:26 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 17:53 UTCEPSS rescore
  18. 2026-06-16 17:53 UTCEPSS rescore
  19. 2026-06-15 17:49 UTCEPSS rescore
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-14 23:18 UTCEPSS rescore
  22. 2026-06-13 23:00 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-11 14:00 UTCEPSS rescore
  26. 2026-06-10 22:18 UTCEPSS rescore
  27. 2026-06-10 13:22 UTCEPSS rescore
  28. 2026-06-10 13:22 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-08 14:17 UTCEPSS rescore
  31. 2026-06-07 15:25 UTCEPSS rescore
  32. 2026-06-07 15:25 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-05 22:47 UTCEPSS rescore
  36. 2026-06-05 06:10 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-04 13:12 UTCEPSS rescore
  39. 2026-06-04 13:12 UTCEPSS rescore
  40. 2026-06-02 19:47 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48596?
CVE-2026-48596 is a low vulnerability published on June 2, 2026. Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in elixir-tesla tesla allows HTTP header injection via Tesla.Multipart.addcontenttype_param/2. Tesla.Multipart.addcontenttypeparam/2 appends caller-supplied strings to the multipart…
When was CVE-2026-48596 disclosed?
CVE-2026-48596 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48596 actively exploited?
CVE-2026-48596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48596?
CVE-2026-48596 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-48596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48596, 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-48596

Explore →

Is Your Infrastructure Affected by CVE-2026-48596?

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

Start Free Scan →Browse All CVEs