{"answers":{"affected":"2 open source packages ship an affected version, including binary-parser. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1245 exists.","fix":"Upgrade binary-parser to 2.3.0 or later.","what":"CVE-2026-1245 is a medium-severity code injection vulnerability in binary-parser, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-1245 and fix it if it is affected.\n\nWhat it is: CVE-2026-1245 is a medium-severity code injection vulnerability in binary-parser, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1245 exists.\n\nAffected packages and fixed versions:\n- binary-parser (npm): affected all versions; fixed in 2.3.0\n- binary-parser (npm): affected all versions; fixed in 2.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-1245/ (Markdown: https://insights.sbomify.com/CVE-2026-1245/index.md)","id":"CVE-2026-1245","markdown":"https://insights.sbomify.com/CVE-2026-1245/index.md","name":"CVE-2026-1245","record":{"aliases":["GHSA-m39p-34qh-rh3w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js binary parser","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript code via unsanitized parser field names or encoding parameters in the binary-parser library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"binary-parser","vendor":"keichi"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"CVE-2026-1245","id":"CVE-2026-1245","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"ShortPixel Image Optimizer \u003c= 6.4.2 - Authenticated (Editor+) Arbitrary File Read via 'loadFile' Parameter","id":"CVE-2026-1246"},"packages":[{"ecosystem":"npm","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"binary-parser","purl":null,"source":"GHSA-m39p-34qh-rh3w"},{"ecosystem":"npm","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"binary-parser","purl":"pkg:npm/binary-parser","source":"GHSA-m39p-34qh-rh3w"}],"prev":{"headline":"Forms Bridge \u003c= 4.2.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'id' Shortcode Attribute","id":"CVE-2026-1244"},"products":["binary-parser"],"published":"2026-01-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-21","vendors":["binary-parser"]},"summary":"Attackers can execute arbitrary JavaScript code via unsanitized parser field names or encoding parameters in the binary-parser library.","url":"https://insights.sbomify.com/CVE-2026-1245/"}