{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2025-23090 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 20.18.2, 22.13.1 or 23.8.0.","what":"CVE-2025-23090 is a vulnerability in node, published on 22 Jan 2025."},"fix_prompt":"Check this codebase for CVE-2025-23090 and fix it if it is affected.\n\nWhat it is: CVE-2025-23090 is a vulnerability in node, published on 22 Jan 2025. \nExploitation: There is no known exploitation of CVE-2025-23090 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected from 19.0.0; fixed in 20.18.2, 22.13.1, 23.8.0\n- node-min (Bitnami): affected from 19.0.0; fixed in 20.18.2, 22.13.1, 23.8.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-2025-23090/ (Markdown: https://insights.sbomify.com/CVE-2025-23090/index.md)","id":"CVE-2025-23090","markdown":"https://insights.sbomify.com/CVE-2025-23090/index.md","name":"CVE-2025-23090","record":{"aliases":["BIT-node-2025-23090","BIT-node-min-2025-23090","GHSA-5vvm-wqc8-r5m8","MINI-298h-qwf7-x6h9","MINI-hw8j-ccj9-66jc","MINI-vm76-2frg-jmq4"],"analysis":null,"analysis_generated_by":null,"assigner":"hackerone","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This CVE record has been withdrawn due to a duplicate entry CVE-2025-23083.","ecosystems":["Bitnami"],"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":"This CVE record has been withdrawn due to a duplicate entry CVE-2025-23083.","id":"CVE-2025-23090","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2025"},"n_packages":2,"n_references":0,"next":{"headline":"Security feature bypass in EFG","id":"CVE-2025-23091"},"packages":[{"ecosystem":"Bitnami","fixed":["20.18.2","22.13.1","23.8.0"],"introduced":["19.0.0","21.0.0","23.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2025-23090"},{"ecosystem":"Bitnami","fixed":["20.18.2","22.13.1","23.8.0"],"introduced":["19.0.0","21.0.0","23.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2025-23090"}],"prev":{"headline":"This Record was REJECTED after determining it is not in compliance with CVE Program requirements regarding assignment for vulnerabilities","id":"CVE-2025-23089"},"products":[],"published":"2025-01-22","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2025-07-18","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-23090/"}