CVE-2026-54054: transmute · Server-Side Request Forgery (SSRF)
Affects transmuteSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.3.0 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade transmute and transmute-app/transmute to 1.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| transmute-apptransmute | Affected
| Fixed in
|
GitHubtransmute-app/transmutepkg:github/transmute-app/transmuteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade transmute to version 1.3.0 or later, where this SSRF vulnerability is fixed. No other mitigation is indicated or required according to the available data.
Description
Transmute versions prior to 1.3.0 contain a Server-Side Request Forgery (SSRF) vulnerability in the URL import endpoint. This flaw allows authenticated or guest users to make the server perform HTTP requests to internal or cloud-local network resources. The vulnerability arises because the HTTP downloader follows redirects and does not validate target addresses. Downloaded content is stored and accessible, enabling full-read SSRF. The issue is fixed in version 1.3.0.