Vulnerability in swoosh (CVE-2026-54893)
Summary
Vulnerability in swoosh (CVE-2026-54893). Risk of unauthorized operations or information disclosure. Exploitable via Swoosh.Adapters.MsGraph. Mitigation: upgrade to 1.26.3 or later.
Original description
The description as published by the source.
Summary
Swoosh.Adapters.MsGraph builds its Microsoft Graph API request URL by interpolating the sender's email address directly into the URL path (/users/{from}/sendMail) without percent-encoding or validation. In applications that derive the from address from untrusted or user-influenced input (a relay, a contact form, or a "send as" feature), an attacker can inject URL-special characters into the local part of the address to escape the intended path segment and rewrite the request's path and query string. Because the rewritten request is still sent as the application's authenticated POST with its Microsoft Graph bearer token, the attacker can redirect it to other Graph endpoints within the token's scopes.
Details
The flaw is in lib/swoosh/adapters/ms_graph.ex. api_endpoint_url/2 constructs the Graph endpoint by interpolating the email's from address into the path /users/{from}/sendMail. The from value is taken verbatim from the email struct and is neither percent-encoded nor validated against the RFC 5321 character set before being placed into the URL. deliver/2 then issues an authenticated POST to that constructed URL using the application's Graph bearer token.
Because the address sits as the local part of /users/{from}/sendMail, characters such as /, ?, and # are not neutralized. A / lets the attacker append or replace additional path segments, a ? starts an attacker-controlled query string, and # truncates the remainder of…
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-54893 has been found in swoosh.
Attackers can target a specific entry point like Swoosh.Adapters.MsGraph over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade swoosh to 1.26.3 or later.
If unsure, ask your IT team or search "swoosh CVE-2026-54893" on the vendor's site.
CVE-2026-54893 (swoosh) — CWE-116
Attack surface: Swoosh.Adapters.MsGraph / from / POST
Patched: 1.26.3 — apply immediately
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 swoosh. Attackers reach the vulnerable code path via Swoosh.Adapters.MsGraph.
Check the vendor advisory for the affected versions of swoosh. Attack surface: Swoosh.Adapters.MsGraph / from / POST.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.26.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'swoosh' . 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 'swoosh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
swooshを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade swoosh to 1.26.3ステージング環境で 1.26.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web cna.erlef.org
- web github.com
- web github.com
- web osv.dev
- web github.com
- web nvd.nist.gov
- web github.com