# CVE-2026-62857: Fedify: Server-Side Request Forgery in getNodeInfo() Allows Access to Internal Network Resources

> Attacker-controlled URLs in Fedify's getNodeInfo() allow accessing internal network resources and reading their responses.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 8 Aug 2026
- **Also known as:** GHSA-hqph-j65v-8cq5

## What is CVE-2026-62857?

CVE-2026-62857 is a high-severity server-side request forgery vulnerability in fedify-dev fedify, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fedify is a TypeScript library for building federated server apps powered by ActivityPub. From version 1.2.0 through the affected 1.9, 1.10, 2.0, 2.1, 2.2, and 2.3 maintenance lines, getNodeInfo() follows an attacker-controlled links[].href value from /.well-known/nodeinfo without scheme, redirect, or private-address validation, allowing requests to loopback, link-local, cloud metadata, and private-network services and returning their response bodies. This issue is fixed in versions 1.9.13, 1.10.12, 2.0.22, 2.1.18, 2.2.7, and 2.3.2.

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

## Which versions are affected by CVE-2026-62857?


## How do I fix CVE-2026-62857?

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

## Is CVE-2026-62857 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62857 and fix it if it is affected.

What it is: CVE-2026-62857 is a high-severity server-side request forgery vulnerability in fedify-dev fedify, published on 6 Aug 2026. 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-2026-62857 exists.

Affected product: fedify-dev fedify. 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-2026-62857/ (Markdown: https://insights.sbomify.com/CVE-2026-62857/index.md)
```

## Sources

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

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