Security readout for executives and security teams
Plain-English summary
CVE-2026-1245 affects the Node.js binary-parser library. If an application lets untrusted input control parser field names or encoding parameters, that input may be executed as JavaScript inside the application process. Business urgency depends on whether your applications use this library with attacker-controlled parser definitions.
Executive priority
Treat this as a targeted dependency remediation, not an internet-wide emergency. Prioritize applications that parse attacker-supplied data or accept externally supplied parser schemas. If binary-parser is not used, or parser definitions are fully static and trusted, urgency is lower.
Technical view
binary-parser before version 2.3.0 interpolates field names and encoding parameters into dynamically generated JavaScript without sanitization. This is classified as code injection under CWE-94 and CWE-95. The CVSS 3.1 score is 6.5, network exploitable with low complexity and no privileges or user interaction, but rated limited confidentiality and integrity impact.
Likely exposure
Exposure is most likely in Node.js services that use binary-parser and build parser definitions from user-controlled or externally supplied data. Applications using only static, trusted parser definitions appear less exposed based on the provided description.
Exploitation context
The source bundle does not indicate active exploitation, public weaponization, or CISA KEV listing. Exploitation requires an application pattern where untrusted values reach parser field names or encoding parameters.
Researcher notes
The key validation question is data flow: can an attacker influence field names or encoding parameters passed into binary-parser? The provided sources identify version 2.3.0 as the boundary but do not provide evidence of exploitation in the wild.
Mitigation direction
- Inventory Node.js projects for the binary-parser package.
- Upgrade binary-parser to version 2.3.0 or later where applicable.
- Do not allow untrusted input to define parser field names or encodings.
- Review vendor and CERT guidance for any updated remediation details.
- Rebuild and redeploy affected applications after dependency updates.
Validation and detection
- Check package manifests and lockfiles for binary-parser versions below 2.3.0.
- Search code for dynamic parser construction using external input.
- Confirm production builds include the remediated dependency version.
- Run dependency scanning after updating packages.
- Review logs for unusual parser-related errors or unexpected code execution indicators.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/keichi/binary-parser/pull/283CVE reference
- https://github.com/keichi/binary-parserCVE reference
- https://www.npmjs.com/package/binary-parserCVE reference
- https://kb.cert.org/vuls/id/102648CVE reference
- https://www.kb.cert.org/vuls/id/102648CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.