CVE-2026-55246
7.8HighPublished 15 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Impact
- Full C/I/A compromise
- Weakness
- CWE-122, CWE-787
Impact
Attackers can corrupt the heap to crash the host application or potentially execute arbitrary code. They need a user or service to parse an attacker-supplied .binarycookies file.
Root cause
The parser uses an untrusted page count header field as a loop bound without bounds checking against the allocated buffer, causing out-of-bounds heap reads and writes.
Affected systems
bincookie prior to 0.1.9
CVSS v3.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade the bincookie header dependency to version 0.1.9 or later. If patching immediately is not possible, reject untrusted .binarycookies files before parsing.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.