Skip to main content
← Vulnerabilities

Silent loss of messages when merging overlapping chat exports in whatstk

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

1.8LowCNA
Exploited
No known exploitation
Fix
Fixed in 0.9.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.9.0.

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity1.8/10CVSS 1.8
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

CVE-2026-121564 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.8 (low) and affects whatstk; fixed in 0.9.0.

Published
Last modified
Published
Not listed in CISA KEV
12/100 · provisional
Fix
Fixed in 0.9.0
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

The whatstk Python library for processing WhatsApp chat exports is affected, specifically its chat-merging feature across versions from 0.3.0 up to (but not including) the fixed release. When two overlapping exports are merged, messages from one export can be silently dropped without any warning, so the merged chat is incomplete, which matters for uses such as forensic review and building training datasets.

Read the original description

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.

What to do

  • Upgrade to a fixed version: 0.9.0.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • whatstkPyPI

    From 0.3.0 · fixed in 0.9.0

Evidence 4

  1. Patch
  2. Patch
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121564

Is CVE-2026-121564 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121564?

whatstk (PyPI): from 0.3.0 before 0.9.0.Source: cve.now feed data

How do I fix CVE-2026-121564?

Upgrade to a fixed version: 0.9.0.Source: cve.now feed data