CVE-2026-107276
MISP Email OTP Race Condition Allows One-Time Password to Be Consumed by Multiple Concurrent Requests
02 Description
MISP Email OTP Race Condition Allows One-Time Password to Be Consumed by Multiple Concurrent Requests
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.21% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 11.4% of scored records. A rank, not a probability.
- NVD base score
- 6.3 (CVSS v4.0), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- NVD analysis status
- Deferred. NVD last modified this record on 2026-10-07.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-07 15:36Z21 DAYS AGO
- Last updated
- 2026-10-07 20:28Z21 DAYS AGO
- Reserved
- 2026-10-07
- Assigning CNA
- CIRCL
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 6.3)
- CNA CVSS vector
- CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
- Weaknesses
- Data version
- 5.2
- Document digest
- c4d5bbd790f5f8e70f02260b96c82290a6c261a31723b0a880bcf03d45abf795
05 Affected products
06 References
- github.comSecurity patchhttps://github.com/MISP/MISP/commit/ba95e67d5
07 Remediation
The fix makes OTP consumption atomic by moving the deletion of the OTP from the shared store into the validation condition itself. The return value of the delete operation (1 if the key was actually removed, 0 otherwise) is now part of the success check, so only the request that successfully removes the OTP from the store is permitted to proceed with login. A session-state cleanup call was also added to remove the OTP user reference from the session.