Quick answers
- Is CVE-2026-116201 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116201 being exploited in the wild.
- How severe is CVE-2026-116201?
- High severity, with a CVSS score of 8.8, published 25 October 2026.
- Which products and versions are affected?
- Snipe-IT before 8.5.0.
- Is there a fix for CVE-2026-116201?
- Yes: fixed in 8.5.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116201 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116201?
- Check whether you run Snipe-IT 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: 8.5.0
Technical details
The vulnerability is a capture-replay flaw combined with a time-of-check time-of-use (TOCTOU) race condition in the SAML assertion handler (/saml/acs). The saml_nonces table uses a non-unique index on the nonce column and lacks transaction-level protection, allowing concurrent POST requests with the same captured assertion to both pass the nonce existence check and both execute Auth::login(), creating two parallel sessions from one assertion. An attacker needs network access to capture a valid SAML assertion (via MITM, malicious browser extension, or log leakage) and the ability to submit the assertion twice within a sub-second race window.
Affected products
- Snipe Snipe-IT before 8.5.0
Timeline
- 2026-10-08: disclosed
- 2026-10-25: advisory