Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

ssrfcheck: SSRF Bypass Caused by Failure to Classify Reserved IP Address Space as Invalid

Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest 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

Source published
5 May 2026 20:29:06 UTC
Source modified
5 May 2026 20:56:27 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS_V4 · 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

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 22:28 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current