# CVE-2025-8267: ssrfcheck SSRF — Fixed in 1.2.0 📦 npm Not in CISA KEV # CVE-2025-8267 — ssrfcheck [Fix: felippe-regazio/ssrfcheck@9507b49](https://github.com/felippe-regazio/ssrfcheck/commit/9507b49fd764f2a1a1d1e3b9ee577b7545e6950e) CVE-2025-8267 is a Server-Side Request Forgery (SSRF) vulnerability in ssrfcheck. A fix is available for ssrfcheck — see the affected versions and patch details below. ssrfcheck: SSRF Bypass Caused by Failure to Classify Reserved IP Address Space as Invalid Also known as[GHSA-p4hc-9pjh-55c8](/vulnerability/GHSA-p4hc-9pjh-55c8) Published Jul 28, 2025 Updated Nov 4, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### Proof-of-concept exploit code exists - CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation. - CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-8267. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.5%probability of exploitation in next 30 days Lower Risk+0.03% Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk 0.00%0.33%0.67%1.00%0.1%0.5%Apr 26Aug 26Oct 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 1 pkg affected How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched. 2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream `ssrfcheck`npm 10Kdownloads / week ## Description ## SSRF Bypass in `ssrfcheck` - fails to classify reserved IP address space as invalid `ssrfcheck` is an npm package that serves to provide protection from SSRF by validating URLs or hostname inputs. Resources: - Project's GitHub code repository: [https://github.com/felippe-regazio/ssrfcheck](https://github.com/felippe-regazio/ssrfcheck) - Project's npm package: [https://www.npmjs.com/package/ssrfcheck](https://www.npmjs.com/package/ssrfcheck) ### Vulnerability The `ssrfcheck` package maintains a denylist of IP addresses and ranges to check against when validating if an IP address is to be considered as safe or not. However, the IP address list used for the denylist is incomplete and misses a reserved IP address space as defined by the IANA (Internet Assigned Numbers Authority): - 224.0.0.0/4 - Multicast Practically, this reserved IP address space is used for multicast traffic and would most commonly be used for reserved local communication over network protocols such as UDP, which would make it less likely to be used in a typical SSRF attack in practice. However, such reserved IP address space shouldn't be allowed and it would be responsible of the SSRF protection package to align and conform to an agreed-upon standard of special-purposed addresses that should not be considered a valid public IP address. For reference, the popular npm packages `private-ip` and `ipaddr.js` that are highly dependent-upon to make decisions about SSRF protection and both consider the above mentioned IP address space as reserved and is not considered a valid public IP address. ### Exploit Proof of Concept 1. Install the `ssrfcheck` package: ``` npm install ssrfcheck ``` 1. Define an `app.js` file with the programmatic API of `ssrfcheck`: ``` import { isSSRFSafeURL } from 'ssrfcheck'; let result result = isSSRFSafeURL('https://012.1.2.3/whatever'); console.log(result); // returns false result = isSSRFSafeURL('https://localhost:8080/whatever'); console.log(result); // returns false result = isSSRFSafeURL('https://239.255.255.250:8080/whatever'); console.log(result); // returns true - bypassed ``` ### Vulnerable versions All versions of ssrfcheck are vulnerable to this issue, up to and including to the latest version of `1.1.1`. ### Assigned CVE [CVE-2025-8267](https://nvd.nist.gov/vuln/detail/CVE-2025-8267) ## Author Liran Tal ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 📦npm `ssrfcheck` all versions 1.2.0`npm install ssrfcheck@1.2.0` ## Affected Products 1 product · 1 configurations Application `ssrf check`felipperegazio < 1.2.0 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ssrfcheck, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update ssrfcheck to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-8267 is resolved across your whole dependency graph. 3. ### Workarounds Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated. ## Frequently Asked Questions \# SSRF Bypass in \`ssrfcheck\` - fails to classify reserved IP address space as invalid \`ssrfcheck\` is an npm package that serves to provide protection from SSRF by validating URLs or hostname inputs. Resources: \* Project's GitHub code repository: https://github.com/felippe-regazio/ssrfcheck \* Project's npm package: https://www.npmjs.com/package/ssrfcheck ## Vulnerability The \`ssrfcheck\` package maintains a denylist of IP addresses and ranges to check against when validating if an IP address is to be considered as safe or not. However, the IP address list used for the denylist is incomp O3 Security · Impact-Aware SCA ### Is CVE-2025-8267 in your dependencies? Find it across npm, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)