# CVE-2025-8020: private-ip vulnerable to Server-Side Request Forgery

> Attackers can bypass private IP restrictions by using multicast addresses, potentially accessing internal network resources.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2025
- **Updated:** 22 Aug 2026
- **Also known as:** CLSA-2026-1791834096, GHSA-9h3q-32c7-r533

## What is CVE-2025-8020?

CVE-2025-8020 is a high-severity server-side request forgery vulnerability in private-ip, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of the package private-ip are vulnerable to Server-Side Request Forgery (SSRF) where an attacker can provide an IP or hostname that resolves to a multicast IP address (224.0.0.0/4) which is not included as part of the private IP ranges in the package's source code.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-8020?

2 open source packages ship an affected version, including private-ip.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `private-ip` | npm | All versions to 3.0.2 | None |
| `private-ip` | npm | All versions to 3.0.2 | None |

## How do I fix CVE-2025-8020?

Upgrade to a fixed version.

## Is CVE-2025-8020 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8020 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8020 and fix it if it is affected.

What it is: CVE-2025-8020 is a high-severity server-side request forgery vulnerability in private-ip, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8020 exists.

Affected packages and fixed versions:
- private-ip (npm): affected all versions up to 3.0.2; no fix listed
- private-ip (npm): affected all versions up to 3.0.2; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8020/ (Markdown: https://insights.sbomify.com/CVE-2025-8020/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8020
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8020
- OSV: https://osv.dev/vulnerability/CVE-2025-8020

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8020/
Summaries are generated and may contain mistakes; the official description above is the record.