CVE-2026-50131 is a server-side request forgery protection bypass in Fedify, a TypeScript library for building ActivityPub-based federated server applications. The flaw is in the public-address validation logic used before runtime document and media fetching, specifically in validatePublicUrl() and its IPv4 classification helper isValidPublicIPv4Address(). Starting in version 0.11.2 and before fixed releases 1.9.12, 1.10.11, 2.0.19, 2.1.15, and 2.2.4, the implementation attempted to determine whether a destination was public by excluding only a limited set of private and local IPv4 ranges. While it blocked common ranges such as loopback, link-local, RFC1918 private space, and some local-use addresses, it failed to reject multiple other non-public or special-use ranges, including carrier-grade NAT, benchmarking, documentation, multicast, and future-reserved space. The IPv6 handling was also described as incomplete for transition and tunneling cases, including NAT64-wrapped private destinations. Because this validation served as an SSRF defense before outbound fetches, an attacker could supply crafted remote resource URLs that resolve to addresses incorrectly treated as public, thereby bypassing the intended restriction and reaching internal or local network resources.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.