CVE-2026-62857
SSRF in Fedify nodeinfo handling allows internal/metadata data retrieval.
Is CVE-2026-62857 being exploited?
Not confirmed. CVE-2026-62857 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-62857?
CVE-2026-62857 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62857?
Yes. A fix has been recorded for CVE-2026-62857. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62857 affect?
CVE-2026-62857 affects Fedify < 1.9.13, Fedify < 1.10.12, Fedify < 2.0.22, Fedify < 2.1.18, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62857?
Upgrade to fixed versions or validate/block nodeinfo hrefs and private/cloud metadata access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Server-Side Request Forgery: attacker can force requests to loopback, link-local, cloud metadata, and private-network services and read responses.
Immediate action required
- affected>= 1.2.0 and < 1.9.13
- affected>= 1.10.0 and < 1.10.12
- affected>= 2.0.0 and < 2.0.22
- affected>= 2.1.0 and < 2.1.18
- affected>= 2.2.0 and < 2.2.7
- affected>= 2.3.0 and < 2.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.