Quick answers
- Is CVE-2026-104901 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104901 being exploited in the wild.
- How severe is CVE-2026-104901?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- MISP Project MISP before 2.5.48.
- Is there a fix for CVE-2026-104901?
- Yes: fixed in 2.5.48. Until then: Restrict configuration of linked remote MISP servers to trusted sources only, or disable the ID Translator feature until the instance can be upgraded.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-02"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104901 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104901?
- Check whether you run MISP Project MISP 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.5.48
Restrict configuration of linked remote MISP servers to trusted sources only, or disable the ID Translator feature until the instance can be upgraded.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-02"}]
Technical details
The ID Translator feature renders event IDs returned from remote linked MISP servers without output encoding, allowing injection of arbitrary HTML and JavaScript. An attacker controlling or compromising a configured remote MISP server can craft responses containing XSS payload that executes in the browser context of authenticated users who visit the ID Translator page. The fix involves casting event IDs to integers and escaping output in both UI themes.
Affected products
- MISP Project MISP before 2.5.48