Quick answers
- Is CVE-2026-103655 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103655 being exploited in the wild.
- How severe is CVE-2026-103655?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Misp < 2.5.48.
- Is there a fix for CVE-2026-103655?
- Yes: fixed in 2.5.48 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103655 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-103655?
- Check whether you run 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 and later
Technical details
The vulnerability exists in the TOTP verification logic within MISP's user login flow, where the system fails to record whether a given TOTP time period has been consumed. This allows the same valid code to be accepted multiple times within its validity window. An attacker must intercept a legitimate TOTP code (via network interception, shoulder surfing, or compromised client) and replay it within the code's validity period; the attack requires the target user to have TOTP enabled.
Affected products
- MISP MISP < 2.5.48
Timeline
- 2026-10-01: disclosed