{"answers":{"affected":"2 open source packages ship an affected version, including seroval. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23737 in the wild and no public exploit code.","fix":"Upgrade seroval to 1.4.1 or later.","what":"CVE-2026-23737 is a high-severity unsafe deserialization vulnerability in lxsmnsyc seroval, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-23737 and fix it if it is affected.\n\nWhat it is: CVE-2026-23737 is a high-severity unsafe deserialization vulnerability in lxsmnsyc seroval, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-23737 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- seroval (npm): affected all versions; fixed in 1.4.1\n- seroval (npm): affected all versions; fixed in 1.4.1\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-23737/ (Markdown: https://insights.sbomify.com/CVE-2026-23737/index.md)","id":"CVE-2026-23737","markdown":"https://insights.sbomify.com/CVE-2026-23737/index.md","name":"CVE-2026-23737","record":{"aliases":["GHSA-3rxj-6cgf-8cfw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript serialization library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript code by exploiting improper input handling in the seroval library's JSON deserialization functions.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"seroval","vendor":"lxsmnsyc"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, improper input handling in the JSON deserialization component can lead to arbitrary JavaScript code execution. Exploitation is possible via overriding constant value and error deserialization, allowing indirect access to unsafe JS evaluation. At minimum, attackers need the ability to perform 4 separate requests on the same function, and partial knowledge of how the serialized data is used during later runtime processing. This vulnerability affects the fromJSON and fromCrossJSON functions in a client-to-server transmission scenario. This issue has been fixed in version 1.4.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"seroval Affected by Remote Code Execution via JSON Deserialization","id":"CVE-2026-23737","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Cross-site scripting in asterisk","id":"CVE-2026-23738"},"packages":[{"ecosystem":"npm","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"seroval","purl":null,"source":"GHSA-3rxj-6cgf-8cfw"},{"ecosystem":"npm","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"seroval","purl":"pkg:npm/seroval","source":"GHSA-3rxj-6cgf-8cfw"}],"prev":{"headline":"seroval Affected by Prototype Pollution via JSON Deserialization","id":"CVE-2026-23736"},"products":["seroval"],"published":"2026-01-21","related":[{"cvss_score":7.5,"headline":"seroval affected by Denial of Service via RegExp serialization","id":"CVE-2026-23956","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.5,"headline":"seroval is vulnerable to Denial of Service via array serialization","id":"CVE-2026-23957","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.5,"headline":"Seroval affected by Denial of Service via Deeply Nested Objects","id":"CVE-2026-24006","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.3,"headline":"seroval Affected by Prototype Pollution via JSON Deserialization","id":"CVE-2026-23736","kev_date_added":null,"published":"2026-01-21"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["lxsmnsyc"]},"summary":"Attackers can execute arbitrary JavaScript code by exploiting improper input handling in the seroval library's JSON deserialization functions.","url":"https://insights.sbomify.com/CVE-2026-23737/"}