{"answers":{"affected":"2 open source packages ship an affected version, including ssrfcheck. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8267 exists.","fix":"Upgrade ssrfcheck to 1.2.0 or later.","what":"CVE-2025-8267 is a high-severity server-side request forgery vulnerability in ssrfcheck, published on 28 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8267 and fix it if it is affected.\n\nWhat it is: CVE-2025-8267 is a high-severity server-side request forgery vulnerability in ssrfcheck, published on 28 Jul 2025. 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-2025-8267 exists.\n\nAffected packages and fixed versions:\n- ssrfcheck (npm): affected all versions; fixed in 1.2.0\n- ssrfcheck (npm): affected all versions; fixed in 1.2.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-8267/ (Markdown: https://insights.sbomify.com/CVE-2025-8267/index.md)","id":"CVE-2025-8267","markdown":"https://insights.sbomify.com/CVE-2025-8267/index.md","name":"CVE-2025-8267","record":{"aliases":["GHSA-p4hc-9pjh-55c8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"npm SSRF validation library","requires_auth":"none","summary":"Attackers can bypass SSRF protections in the ssrfcheck library by targeting multicast IP addresses due to an incomplete denylist.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"ssrf_check","vendor":"felipperegazio"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Versions of the package ssrfcheck before 1.2.0 are vulnerable to Server-Side Request Forgery (SSRF) due to an incomplete denylist of IP address ranges. Specifically, the package fails to classify the reserved IP address space 224.0.0.0/4 (Multicast) as invalid. This oversight allows attackers to craft requests targeting these multicast addresses.","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":"ssrfcheck: SSRF Bypass Caused by Failure to Classify Reserved IP Address Space as Invalid","id":"CVE-2025-8267","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":2,"n_references":4,"next":{"headline":"Ai Engine \u003c= 2.9.5 - Missing Authorization to Unauthenticated Uploaded Files Disclosure And Deletion","id":"CVE-2025-8268"},"packages":[{"ecosystem":"npm","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"ssrfcheck","purl":null,"source":"GHSA-p4hc-9pjh-55c8"},{"ecosystem":"npm","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"ssrfcheck","purl":"pkg:npm/ssrfcheck","source":"GHSA-p4hc-9pjh-55c8"}],"prev":{"headline":"yanyutao0402 ChanCMS collect.js getArticle deserialization","id":"CVE-2025-8266"},"products":["ssrfcheck"],"published":"2025-07-28","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":"2025-07-28","vendors":["n/a"]},"summary":"Attackers can bypass SSRF protections in the ssrfcheck library by targeting multicast IP addresses due to an incomplete denylist.","url":"https://insights.sbomify.com/CVE-2025-8267/"}