Transmute has full-read SSRF in URL file import (POST /api/files/url) — no host/IP validation, follows redirects
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| transmute-app | transmute | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Transmute-app | Transmute |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.354% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Transmute-app
Transmute-app transmute |
|
| Vendors & Products |
Transmute-app
Transmute-app transmute |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Transmute has full-read SSRF in URL file import (POST /api/files/url) — no host/IP validation, follows redirects | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|