cve.bz

CVE-2026-50131 fedify-dev: SSRF

8.6 highEPSS 0.4%Fix available

High (8.6) in fedify-dev. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @fedify/fedify 1.10.11, 1.9.12, 2.0.19.

On this page
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.

Severity

CVSS 3.1

8.6 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-06-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-918 Server-Side Request Forgery (SSRF)
CWE-1286 Improper Validation of Syntactic Correctness of Input
CWE-1389 Incorrect Parsing of Numbers with Different Radices
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @fedify/fedify (npm): fixed in 1.9.12, 1.10.11, 2.0.19, 2.1.15, 2.2.4
  • @fedify/vocab-runtime (npm): fixed in 2.0.19, 2.1.15, 2.2.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-50131 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50131?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50131?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50131 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
fedify-dev fedify>= 0.11.2, < 1.9.12
fedify-dev fedify>= 1.10.0, < 1.10.11
fedify-dev fedify>= 2.0.0, < 2.0.19
fedify-dev fedify>= 2.1.0, < 2.1.15
fedify-dev fedify>= 2.2.0, < 2.2.4
fedify-dev vocab-runtime< 2.0.19
fedify-dev vocab-runtime>= 2.1.0, < 2.1.15
fedify-dev vocab-runtime>= 2.2.0, < 2.2.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xw9q-2mv6-9fr8npm@fedify/fedify>=0.11.2 <1.9.121.9.12
GHSA-xw9q-2mv6-9fr8npm@fedify/fedify>=1.10.0 <1.10.111.10.11
GHSA-xw9q-2mv6-9fr8npm@fedify/fedify>=2.0.0 <2.0.192.0.19
GHSA-xw9q-2mv6-9fr8npm@fedify/fedify>=2.1.0 <2.1.152.1.15
GHSA-xw9q-2mv6-9fr8npm@fedify/fedify>=2.2.0 <2.2.42.2.4
GHSA-xw9q-2mv6-9fr8npm@fedify/vocab-runtime<2.0.192.0.19
GHSA-xw9q-2mv6-9fr8npm@fedify/vocab-runtime>=2.1.0 <2.1.152.1.15
GHSA-xw9q-2mv6-9fr8npm@fedify/vocab-runtime>=2.2.0 <2.2.42.2.4

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-676 NoSQL Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON