{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54054 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54054 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54054 is a medium-severity server-side request forgery vulnerability in transmute-app transmute, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54054 and fix it if it is affected.\n\nWhat it is: CVE-2026-54054 is a medium-severity server-side request forgery vulnerability in transmute-app transmute, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54054 in the wild and no public exploit code.\n\nAffected product: transmute-app transmute. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54054/ (Markdown: https://insights.sbomify.com/CVE-2026-54054/index.md)","id":"CVE-2026-54054","markdown":"https://insights.sbomify.com/CVE-2026-54054/index.md","name":"CVE-2026-54054","record":{"aliases":["GHSA-89m5-mvmx-7xrf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"File conversion tool","requires_auth":"low_privilege","summary":"An authenticated user can exploit a Server-Side Request Forgery vulnerability in the URL import endpoint to read internal or cloud-local resources via the server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Transmute is a free, open-source, self-hosted file conversion and compression tool. Prior to version 1.3.0, Transmute's URL import endpoint, `POST /api/files/url`, is vulnerable to Server-Side Request Forgery (SSRF). The HTTP downloader used by this endpoint fetches user-supplied URLs with redirects enabled and does not validate whether the target resolves to a public, external address. As a result, an authenticated user (or guest user if they are enabled) may be able to cause the Transmute server to make HTTP requests to internal or cloud-local resources from the server's network position. Because downloaded content is stored and can later be retrieved through `GET /api/files/{id}`, this issue can result in full-read SSRF rather than blind SSRF. This is fixed in version 1.3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Transmute has full-read SSRF in URL file import (POST /api/files/url) — no host/IP validation, follows redirects","id":"CVE-2026-54054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Kitty has an Arbitrary File Write via Symlink Race Condition in File Transmission Protocol","id":"CVE-2026-54055"},"packages":[],"prev":{"headline":"Many Notes: Path Traversal via ZIP import allows arbitrary file write and stored XSS in other users' vaults","id":"CVE-2026-54053"},"products":["transmute"],"published":"2026-09-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-11","vendors":["transmute-app"]},"summary":"An authenticated user can exploit a Server-Side Request Forgery vulnerability in the URL import endpoint to read internal or cloud-local resources via the server.","url":"https://insights.sbomify.com/CVE-2026-54054/"}