Vulnerability in tesla (CVE-2026-48596)
Summary
Vulnerability in tesla (CVE-2026-48596). Risk of unauthorized operations or information disclosure. Exploitable via multipart.content_type_params. Mitigation: upgrade to 1.18.3 or later.
Original description
The description as published by the source.
Summary
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.
Workarounds
Validate content-type parameter strings before passing them to Tesla.Multipart.add_content_type_param/2, rejecting any value that contains \r or \n.
Configurations
The application must pass untrusted input into Tesla.Multipart.add_content_type_param/2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48596 has been found in tesla.
Attackers can target a specific entry point like multipart.content_type_params over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade tesla to 1.18.3 or later.
If unsure, ask your IT team or search "tesla CVE-2026-48596" on the vendor's site.
CVE-2026-48596 (tesla) — CWE-113 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: multipart.content_type_params / Multipart / tesla
Patched: 1.18.3 — apply immediately
Workaround: Validate content-type parameter strings before passing them to Tesla.Multipart.add_content_type_param/2, rejecting any value that contains \r or \n.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-113) exists in tesla. Attackers reach the vulnerable code path via multipart.content_type_params without authentication.
Check the vendor advisory for the affected versions of tesla. Attack surface: multipart.content_type_params / Multipart / tesla.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 1.18.3.
Workaround: Validate content-type parameter strings before passing them to Tesla.Multipart.add_content_type_param/2, rejecting any value that contains \r or \n.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tesla' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tesla' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
teslaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Validate content-type parameter strings before passing them to `Tesla.Multipart.add_content_type_param/2`, rejecting any value that contains `\r` or `\n`.パッチが適用されるまでの応急処置として、Validate content-type parameter strings before passing them to
Tesla.Multipart.add_content_type_param/2, rejecting any value that contains\ror\n. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade tesla to 1.18.3ステージング環境で 1.18.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package hex.pm
- package github.com
- patch github.com
- web cna.erlef.org
- web osv.dev
- web github.com
- web github.com