Quick answers
- Is CVE-2026-59188 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59188 being exploited in the wild.
- How severe is CVE-2026-59188?
- Medium severity, with a CVSS score of 5.4, published 23 October 2026.
- Which products and versions are affected?
- Part-DB-server <= 2.12.2.
- Is there a fix for CVE-2026-59188?
- Yes: fixed in 2.12.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59188 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59188?
- Check whether you run Part-DB-server 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: 2.12.3
Technical details
The vulnerability is a stored XSS (CWE-79) caused by reliance on user-controlled filename extensions rather than actual file content to determine whether SVG sanitization is needed. An authenticated attacker uploads an SVG payload with a non-SVG extension, passes the extension check, and when viewed inline the server serves it with Content-Type: image/svg+xml, causing browser script execution in the Part-DB origin. The fix detects actual MIME type via file magic bytes and applies proper SVG sanitization regardless of filename.
Affected products
- Part-DB Part-DB-server <= 2.12.2
Timeline
- 2026-07-19: disclosed
- 2026-06-20: patched