Vulnerability in tesla (CVE-2026-48598)
Summary
Vulnerability in tesla (CVE-2026-48598). Risk of unauthorized operations or information disclosure. Exploitable via name. Mitigation: upgrade to 1.18.3 or later.
Original description
The description as published by the source.
Summary
Improper Encoding or Escaping of Output vulnerability in elixir-tesla tesla allows multipart part header injection via unescaped Content-Disposition parameter values.
Tesla.Multipart.part_headers_for_disposition/1 interpolates each disposition parameter as #{k}="#{v}" with no validation of CR (\r), LF (\n), or double-quote characters. The values come verbatim from the caller via Tesla.Multipart.add_field/4 (the name parameter), Tesla.Multipart.add_file/3, and Tesla.Multipart.add_file_content/4 (both the filename parameter and other disposition opts). A " in the value closes the quoted parameter early; a \r\n ends the Content-Disposition header line and starts a new part header (such as a forged Content-Type), or, after a second \r\n, ends the entire part header block and prepends bytes to the part body. The default-filename path in add_file/3 derives the filename via Path.basename/1, which does not strip CR or LF, so any application forwarding a partially-attacker-controlled file path inherits the same issue.
This issue affects tesla: from 0.8.0 before 1.18.3.
Workarounds
Validate disposition parameter values before passing them to Tesla.Multipart.add_field/4, Tesla.Multipart.add_file/3, or Tesla.Multipart.add_file_content/4, rejecting any value that contains \r, \n, or ".
Configurations
The application must pass untrusted input into a disposition parameter of Tesla.Multipart.add_field/4, `Tesla.Multipart…
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-48598 has been found in tesla.
Attackers can target a specific entry point like name 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-48598" on the vendor's site.
CVE-2026-48598 (tesla) — CWE-116 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: name / filename / tesla
Patched: 1.18.3 — apply immediately
Workaround: Validate disposition parameter values before passing them to the multipart API, rejecting any value that contains \r, \n, or ".
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-116) exists in tesla. Attackers reach the vulnerable code path via name without authentication.
Check the vendor advisory for the affected versions of tesla. Attack surface: name / filename / tesla.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 1.18.3.
Workaround: Validate disposition parameter values before passing them to the multipart API, rejecting any value that contains \r, \n, or ".
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 disposition parameter values before passing them to the multipart API, rejecting any value that contains `\r`, `\n`, or `"`.パッチが適用されるまでの応急処置として、Validate disposition parameter values before passing them to the multipart API, rejecting any value that contains
\r,\n, or". を実施。回避策の副作用 (機能低下) を確認した上で。 -
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