Quick answers
- Is CVE-2026-103664 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103664 being exploited in the wild.
- How severe is CVE-2026-103664?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- MISP Project MISP prior to v2.5.48 (post commit 58925dbf0).
- Is there a fix for CVE-2026-103664?
- Yes: fixed in MISP v2.5.48 and later (commit 58925dbf0). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103664 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-103664?
- 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: MISP v2.5.48 and later (commit 58925dbf0)
Technical details
A reflected XSS vulnerability exists in MISP's analyst data view where the seed path parameter is passed directly into inline JavaScript without sanitization or type enforcement. An authenticated user must be socially engineered to visit a malicious URL containing the payload. The vulnerability was fixed by casting the seed parameter to an integer in both the controller and analyst data elements (commit 58925db).
Affected products
- MISP Project MISP prior to v2.5.48 (post commit 58925dbf0)
Timeline
- 2026-10-01: disclosed