---
id: CVE-2026-55246
title: bincookie is a header-only binarycookies parser
summary: >-
  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 byt…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'
cwe:
  - CWE-122
  - CWE-787
vendor: Tatsh
product: bincookie
affected:
  - bincookie < 0.1.9
published: '2026-10-15'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T19:17:40.430'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-55246'
references:
  - url: >-
      https://github.com/Tatsh/bincookie/commit/bc1433c1ee4d0284750ff85c8437f1b8df91ab3b
    label: security-advisories@github.com
  - url: 'https://github.com/Tatsh/bincookie/releases/tag/v0.1.9'
    label: security-advisories@github.com
  - url: 'https://github.com/Tatsh/bincookie/security/advisories/GHSA-22pc-xxw4-q849'
    label: security-advisories@github.com
  - url: 'https://github.com/Tatsh/bincookie/security/advisories/GHSA-22pc-xxw4-q849'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-15T18:27:22.750510Z'
ingestedAt: '2026-10-15T18:23:58.449Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.