Arbitrary JavaScript execution via unsanitized definition values
Published Jan 20, 2026 · Updated Jan 20, 2026
Code injection in Keichi Takahashi binary-parser before 2.3.0 allows remote attackers to execute JavaScript via parser definitions. Parser field names and encoding strings are interpolated into source passed to the Function constructor without validation or sanitization. Exploitation requires an application to build parser definitions from externally supplied values; static, hardcoded definitions are unaffected, and injected code runs with the Node.js process privileges.
Summary
What happened
Code injection in Keichi Takahashi binary-parser before 2.3.0 allows remote attackers to execute JavaScript via parser definitions. Parser field names and encoding strings are interpolated into source passed to the Function constructor without validation or sanitization. Exploitation requires an application to build parser definitions from externally supplied values; static, hardcoded definitions are unaffected, and injected code runs with the Node.js process privileges.
The record
- CVE
- CVE-2026-1245
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- Keichi Takahashi
- Product
- binary-parser
- Classifications
- CWE-94, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo