# CVE-2025-59436: Server-side request forgery in ip

> An SSRF vulnerability in the node-ip library allows bypassing IP validation checks, potentially enabling access to internal resources.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-59436, GHSA-qf5v-q897-m77r, UBUNTU-CVE-2025-59436

## What is CVE-2025-59436?

CVE-2025-59436 is a low-severity server-side request forgery vulnerability in fedorindutny ip, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ip (aka node-ip) package through 2.0.1 (in NPM) might allow SSRF because the IP address value 017700000001 is improperly categorized as globally routable via isPublic. NOTE: this issue exists because of an incomplete fix for CVE-2024-29415.

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

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


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

No fix has been published for CVE-2025-59436 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59436 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59436 is a low-severity server-side request forgery vulnerability in fedorindutny ip, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59436 exists.

Affected product: fedorindutny ip. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-59436/ (Markdown: https://insights.sbomify.com/CVE-2025-59436/index.md)
```

## Sources

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

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