CVE-2025-8267Withdrawn

ssrfcheck · Vulnerability

CVSS 3.1 8.2 HIGHCVSS 4.0 8.8 HIGHEUVD CVSS 4.0 8.8 CVSS 4.0 · [email protected] · Secondary 7.8 HIGHCVSS 3.1 · [email protected] · Secondary 8.2 HIGHCVSS 3.1 · [email protected] · Primary 5.3 MEDIUMCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by ssrfcheck 1.2.0CVSS_V3 CVSS_V4 Publisher rating HIGHFixed by ssrfcheck 1.2.0KEV status unknown

Original advisory

cve-program · CVE-2025-8267

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-22851

Published

Read the publisher's advisory

nvd · CVE-2025-8267

Published

Read the publisher's advisory

osv · GHSA-c2fv-2fmj-9xrx

Withdrawn

### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-p4hc-9pjh-55c8. This link is maintained to preserve external references. ### Original Description Versions of the package ssrfcheck below 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.

Read the publisher's advisory

osv · GHSA-p4hc-9pjh-55c8

Published

# 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 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: ```bash npm install ssrfcheck ``` 2. Define an `app.js` file with the programmatic API of `ssrfcheck`: ```javascript 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

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 05:41:40 UTC