Intel

AIKIDO-2026-11096

@fedify/fedify is vulnerable to Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF)CVE-2026-50131 Published Today

54

Medium Risk

This Affects:

JS@fedify/fedify
0.0.1 - 1.9.11
Fixed in 1.9.12
1.10.0 - 1.10.10
Fixed in 1.10.11
Are you affected? Scan for Free

TL;DR

The validatePublicUrl() function in the document loader applies an incomplete denylist of non-public IP ranges when validating remote URLs. Special-use IPv4 ranges such as shared address space, benchmarking, multicast, reserved, and documentation ranges, and IPv6 translation and tunneling prefixes such as NAT64, Teredo, and 6to4 are not rejected, so a URL pointing at these addresses passes the public-address check. Because the check runs before fetching remote ActivityPub documents and keys, an attacker who can influence a fetched URL can bypass the private-network protection and reach internal or special-use network resources. The fix replaces the checks with CIDR-based matching that rejects these special-use IPv4 ranges and IPv6 tunneling prefixes.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Background info

@fedify/fedify is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 1.9.11 and 1.10.0 - 1.10.10.

How to fix this

Upgrade the @fedify/fedify library to the patch version.