CVE-2026-121564 json
Silent loss of messages when merging overlapping chat exports in whatstk
published 6d ago modified 6d ago also EUVD-2026-115913
- cvss
- 1.8
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Incomplete Comparison with Missing Factors (CWE-1023) in merge_chats() (whatstk/utils/chat_merge.py), reached from BaseChat.merge(), in whatstk from 0.3.0 before 0.9.0 allows a party that supplies the chat exports to cause messages to be absent from the merged output with no indication that anything was removed, because the merge keeps whole the chat whose first message is oldest and appends from the other only the messages that are strictly newer than the last message of the first. Every message of the second chat that falls inside the date range already covered by the first is therefore discarded. The two chats are compared on their date ranges and not on the identity of the individual messages, so a message held by only one of the two exports is dropped whenever its date falls inside the range of the other, and both branches of _merge_two_chats() behave this way. The merged result is returned without a warning and without a count of what was removed. This results in a merged chat that omits messages the inputs contain, in a library whose documented uses include forensic review and the generation of training data.
Patch / fix
- lucasrodes whatstk 0.9.0
- github.com/lucasrodes/whatstk@01d66d8 commit
- github.com/lucasrodes/whatstk#185 pull request
- github.com/lucasrodes/whatstk/releases/tag/v0.9.0 release
Is CVE-2026-121564 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6d ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 1.8 | CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 1.8 | CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/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 |
Affected products
- lucasrodes whatstk
Classification
- Weakness
-
- CWE-1023 Incomplete Comparison with Missing Factors
References
-
github.com
/lucasrodes/whatstk/pull/185
patch
-
github.com
/lucasrodes/whatstk/commit/01d66d8
patch
-
github.com
/lucasrodes/whatstk/releases/tag/v0.9.0
release-notes
-
secur0.com
/en/cna/cve-list/cve-2026-121564-whatstk-merge-message-loss
third-party-advisory, technical-description
Sources
- CVE List CVE-2026-121564
- NVD CVE-2026-121564
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.