CVE-2026-50131: CWE-918: Server-Side Request Forgery (SSRF) in fedify-dev fedify
Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Fedify previously addressed SSRF/internal network access in GHSA-p9cg-vqcc-grcx by adding public URL validation before runtime document and media fetching. However, the IPv4 validation logic present starting in version 0.11.2 and prior to versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 appears incomplete. The `validatePublicUrl()` protection relies on `isValidPublicIPv4Address()` to reject non-public IPv4 destinations. The function blocks common private and local ranges such as `10.0.0.0/8`, `127.0.0.0/8`, `169.254.0.0/16`, `172.16.0.0/12`, and `192.168.0.0/16`, but it still treats several special-use, reserved, multicast, benchmarking, and carrier-grade NAT IPv4 ranges as valid public destinations. Because this validation is used as an SSRF defense before outbound fetches, this appears to be an incomplete mitigation or bypass class for the previous SSRF issue. Versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 contain an updated patch.
AI Analysis
Technical Summary
Fedify previously implemented SSRF protections by validating public URLs before fetching documents and media. However, the IPv4 validation logic in versions >=0.11.2 and <1.9.12, <1.10.11, <2.0.19, <2.1.15, and <2.2.4 is incomplete. The isValidPublicIPv4Address() function blocks common private and local IP ranges but does not block several special-use, reserved, multicast, benchmarking, and carrier-grade NAT IPv4 ranges. Since validatePublicUrl() depends on this function, SSRF protections can be bypassed, allowing an attacker to make server-side requests to unintended internal or reserved IP addresses. The issue is addressed in versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 with updated patches.
Potential Impact
Successful exploitation allows an attacker to perform server-side request forgery (SSRF), potentially accessing internal network resources or services that should be inaccessible. This can lead to information disclosure (high confidentiality impact), limited integrity impact, and limited availability impact. The CVSS score of 8.6 reflects high severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
Updated patched versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 contain fixes for the incomplete IPv4 validation logic and should be applied to remediate this vulnerability. Since no official vendor advisory or patch links are provided, users should verify and upgrade to these fixed versions. Patch status is not yet confirmed by vendor advisory; check the vendor's official resources for the latest remediation guidance.
CVE-2026-50131: CWE-918: Server-Side Request Forgery (SSRF) in fedify-dev fedify
Description
Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Fedify previously addressed SSRF/internal network access in GHSA-p9cg-vqcc-grcx by adding public URL validation before runtime document and media fetching. However, the IPv4 validation logic present starting in version 0.11.2 and prior to versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 appears incomplete. The `validatePublicUrl()` protection relies on `isValidPublicIPv4Address()` to reject non-public IPv4 destinations. The function blocks common private and local ranges such as `10.0.0.0/8`, `127.0.0.0/8`, `169.254.0.0/16`, `172.16.0.0/12`, and `192.168.0.0/16`, but it still treats several special-use, reserved, multicast, benchmarking, and carrier-grade NAT IPv4 ranges as valid public destinations. Because this validation is used as an SSRF defense before outbound fetches, this appears to be an incomplete mitigation or bypass class for the previous SSRF issue. Versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 contain an updated patch.
CVSS v3.1
Score 8.6high
Affected software
pkg:npm/fedify-dev/fedifyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Fedify previously implemented SSRF protections by validating public URLs before fetching documents and media. However, the IPv4 validation logic in versions >=0.11.2 and <1.9.12, <1.10.11, <2.0.19, <2.1.15, and <2.2.4 is incomplete. The isValidPublicIPv4Address() function blocks common private and local IP ranges but does not block several special-use, reserved, multicast, benchmarking, and carrier-grade NAT IPv4 ranges. Since validatePublicUrl() depends on this function, SSRF protections can be bypassed, allowing an attacker to make server-side requests to unintended internal or reserved IP addresses. The issue is addressed in versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 with updated patches.
Potential Impact
Successful exploitation allows an attacker to perform server-side request forgery (SSRF), potentially accessing internal network resources or services that should be inaccessible. This can lead to information disclosure (high confidentiality impact), limited integrity impact, and limited availability impact. The CVSS score of 8.6 reflects high severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
Updated patched versions 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4 contain fixes for the incomplete IPv4 validation logic and should be applied to remediate this vulnerability. Since no official vendor advisory or patch links are provided, users should verify and upgrade to these fixed versions. Patch status is not yet confirmed by vendor advisory; check the vendor's official resources for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-03T18:49:32.275Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a29d0250e53e73883986cde
Added to database: 6/10/2026, 8:59:17 PM
Last enriched: 6/10/2026, 9:13:55 PM
Last updated: 6/10/2026, 11:34:19 PM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.