CVE-2026-121691 Details
Description
Improper Handling of Highly Compressed Data (CWE-409) in the ZIP loader of whatstk from 0.7.0 before 0.9.0 allows a party that supplies a chat export to exhaust the memory and the disk of the process that parses it, because _str_from_file() (whatstk/whatsapp/parser.py) calls zip_ref.extractall() with no bound on the size of the members and no check of the compression ratio, then reads the extracted file in full with f.read(). The only guard on the archive counts the extracted files and raises when there is not exactly one, but it runs after extractall() has already written them, so it does not prevent the cost. _clean_text() then passes the whole text through unicodedata.normalize("NFKD", text), which holds a second copy, and the parse builds a list of regular expression matches and a DataFrame over it, so peak memory is a multiple of the decompressed text rather than of the archive. A ZIP is a documented input of WhatsAppChat.from_source() and df_from_whatsapp(), and is the form in which WhatsApp exports a chat on iOS, so the attacker supplies the whole file. This results in a small upload costing hundreds of megabytes of memory and of disk, and in the process being killed where that exceeds what is available.
A denial-of-service vulnerability has been identified in the ZIP loader of whatstk, specifically in versions 0.7.0 prior to 0.9.0. The issue arises from improper handling of highly compressed data, allowing a party supplying a chat export to exhaust the memory and disk resources of the process that parses it. This is achieved by exploiting the `_str_from_file()` function in the WhatsApp parser, which calls `zip_ref.extractall()` without any limits on the size of the extracted files or checks on the compression ratio. The extracted data is then read in full, causing significant resource consumption. This vulnerability is particularly concerning because a small ZIP file can lead to a large amount of decompressed data, causing the parsing process to be terminated when it exceeds available resources.
Users can upgrade to whatstk version 0.9.0 or later, which includes a patch for this vulnerability. The latest version can be downloaded from the whatstk GitHub repository. For those using an older version, it's recommended to pass a lower `max_size` argument when parsing chat exports on behalf of others, as the default limit still allows a single source of 50 MB.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 10, 2026CISA-ADP
Assessed Nov 16, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/lucasrodes/whatstk/commit/01d66d8 | Secur0 | Source CodeVendor |
| https://github.com/lucasrodes/whatstk/pull/182 | Secur0 | Issue TrackingVendor |
| https://github.com/lucasrodes/whatstk/releases/tag/v0.9.0 | Secur0 | Release NotesVendor |
| https://secur0.com/en/cna/cve-list/cve-2026-121691-whatstk-zip-decompression-bomb | Secur0 | AdvisoryRemedy |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-409 | Improper Handling of Highly Compressed Data (Data Amplification) | Secur0 |
Affected Products
| Product | Versions |
|---|---|
| whatstk | >= 0.7.0, < 0.9.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 16, 2026 | CVE Modified | CISA-ADP |
| Nov 10, 2026 | New CVE Received | Secur0 |
Volerion