Quick answers
- Is CVE-2026-59976 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59976 being exploited in the wild.
- How severe is CVE-2026-59976?
- High severity, with a CVSS score of 8.1, published 12 October 2026.
- Which products and versions are affected?
- ConvertX prior to 0.18.0.
- Is there a fix for CVE-2026-59976?
- Yes: fixed in 0.18.0. Until then: Restrict unauthenticated access to the /convert endpoint by disabling the unauthenticated access configuration option if not required for your use case. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59976 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-59976?
- Check whether you run ConvertX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.18.0
Restrict unauthenticated access to the /convert endpoint by disabling the unauthenticated access configuration option if not required for your use case.
Technical details
ConvertX's /convert endpoint constructs output file paths by unsanitized concatenation of the convert_to parameter with the output directory, allowing directory traversal via sequences like "../" or "..\". An attacker submitting an extensionless image file with a malicious convert_to value can escape the intended output directory and write arbitrary files. The vulnerability requires either authentication or unauthenticated access to be explicitly enabled in the configuration.
Affected products
- ConvertX ConvertX prior to 0.18.0
Timeline
- 2026-10-12: disclosed
- 2026-04-27: patched