Quick answers
- Is CVE-2026-117543 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117543 being exploited in the wild.
- How severe is CVE-2026-117543?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- jDownloads < 4.1.8.
- Is there a fix for CVE-2026-117543?
- Yes: fixed in 4.1.8. Until then: External downloads that require HTTP redirects during server-side retrieval will be rejected; use direct file URLs instead of redirected URLs where possible. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117543 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-117543?
- Check whether you run jDownloads 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: 4.1.8
External downloads that require HTTP redirects during server-side retrieval will be rejected; use direct file URLs instead of redirected URLs where possible.
Technical details
The vulnerability is a server-side request forgery (SSRF) in the external download URL processing logic of jDownloads. Validation of download destination URLs fails to account for HTTP redirects during server-side retrieval, allowing an attacker to craft an external URL that redirects to an internal or prohibited destination. This permits unauthorized server-side requests and response disclosure. The fix in version 4.1.8 adds stricter validation and may reject external downloads requiring HTTP redirects.
Affected products
- jDownloads jDownloads < 4.1.8
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched: Version 4.1.8 released as security update