CVE-2026-55246bincookie: Heap buffer overflow via unvalidated `num_pages` when parsing a `.binarycookies` file
Updated under an hour ago ()
Does this affect you?
It affects Tatsh bincookie. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.22%, higher than 12% of scored CVEs.
Do this next
Free account, 1 product
bincookie is a header-only binarycookies parser. Prior to 0.1.9, bincookie_init_file() in bincookie.h allocates a buffer using the actual .binarycookies file length but trusts the file-controlled num_pages field as the loop bound for byte-swapping page_sizes entries. A crafted file can make the loop read and write beyond the heap allocation, and related unvalidated page sizes and cookie_offsets can drive additional out-of-bounds accesses in page and cookie iteration. Applications that parse an attacker-supplied binarycookies file may crash or suffer heap corruption that can potentially enable code execution. This issue is fixed in version 0.1.9.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-122, CWE-787
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.22% (percentile 12)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Tatsh bincookie tatsh:bincookie (from the name) | before 0.1.9 | CNA record |
References
- https://github.com/Tatsh/bincookie/security/advisories/GHSA-22pc-xxw4-q849x-refsource-confirm
- https://github.com/Tatsh/bincookie/commit/bc1433c1ee4d0284750ff85c8437f1b8df91ab3bx-refsource-misc
- https://github.com/Tatsh/bincookie/releases/tag/v0.1.9x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.