CVE-2026-29178: CWE-918: Server-Side Request Forgery (SSRF) in LemmyNet lemmy
Lemmy, a link aggregator and forum for the fediverse, is vulnerable to server-side request forgery via a dependency on activitypub_federation, a framework for ActivityPub federation in Rust. Prior to version 0.19.16, the GET /api/v4/image/{filename} endpoint is vulnerable to unauthenticated SSRF through parameter injection in the file_type query parameter. An attacker can inject arbitrary query parameters into the internal request to pict-rs, including the proxy parameter which causes pict-rs to fetch arbitrary URLs. This issue has been patched in version 0.19.16.
AI Analysis
Technical Summary
CVE-2026-29178 is a Server-Side Request Forgery (SSRF) vulnerability identified in Lemmy, a federated link aggregator and forum software. The vulnerability arises from Lemmy's dependency on the Rust-based activitypub_federation framework and its interaction with pict-rs, an image proxy service. Specifically, the GET /api/v4/image/{filename} endpoint accepts a file_type query parameter that is improperly sanitized, allowing attackers to inject arbitrary query parameters into internal requests made to pict-rs. Among these parameters is the proxy parameter, which instructs pict-rs to fetch arbitrary URLs. Because this endpoint is unauthenticated, an attacker can exploit this SSRF flaw remotely without any credentials or user interaction. The SSRF can be leveraged to access internal network resources, potentially bypassing firewall restrictions, or to cause denial of service by forcing the server to make numerous or malicious requests. The vulnerability affects all Lemmy versions prior to 0.19.16, where the issue has been patched. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction required, with high impact on integrity but no impact on confidentiality or availability. No known exploits have been reported in the wild as of the publication date. The root cause is insufficient input validation and unsafe parameter forwarding to an internal proxy service.
Potential Impact
The SSRF vulnerability in Lemmy can have significant impacts on organizations running vulnerable instances, especially those exposing the affected endpoint to the internet. Attackers can exploit this flaw to make arbitrary HTTP requests from the Lemmy server, potentially accessing internal services that are otherwise inaccessible externally, such as internal APIs, metadata services in cloud environments, or administrative interfaces. This can lead to information disclosure, unauthorized internal network reconnaissance, and lateral movement within the network. Additionally, attackers could use the SSRF to perform denial of service attacks by overwhelming internal or external resources. Since Lemmy is a federated platform used by communities worldwide, exploitation could disrupt communication and content sharing. The unauthenticated nature of the vulnerability increases the risk, as no credentials are needed to exploit it. Although no active exploitation has been reported, the high CVSS score and ease of exploitation make it a critical risk for organizations relying on Lemmy for federated social networking.
Mitigation Recommendations
The primary mitigation is to upgrade Lemmy to version 0.19.16 or later, where the SSRF vulnerability has been patched. Organizations should prioritize this update to eliminate the unsafe parameter injection. Additionally, administrators should implement network-level controls to restrict outbound HTTP requests from the Lemmy server to only trusted destinations, reducing the impact of potential SSRF exploitation. Employing web application firewalls (WAFs) with rules to detect and block suspicious query parameter patterns targeting the /api/v4/image/ endpoint can provide an additional layer of defense. Monitoring server logs for unusual outbound requests or spikes in traffic to internal services can help detect exploitation attempts. If upgrading immediately is not feasible, temporarily disabling or restricting access to the vulnerable endpoint can reduce exposure. Finally, conducting internal network segmentation and limiting the Lemmy server's access to sensitive internal resources will minimize the potential damage from SSRF attacks.
Affected Countries
United States, Germany, France, United Kingdom, Canada, Australia, Netherlands, Japan, South Korea, Brazil
CVE-2026-29178: CWE-918: Server-Side Request Forgery (SSRF) in LemmyNet lemmy
Description
Lemmy, a link aggregator and forum for the fediverse, is vulnerable to server-side request forgery via a dependency on activitypub_federation, a framework for ActivityPub federation in Rust. Prior to version 0.19.16, the GET /api/v4/image/{filename} endpoint is vulnerable to unauthenticated SSRF through parameter injection in the file_type query parameter. An attacker can inject arbitrary query parameters into the internal request to pict-rs, including the proxy parameter which causes pict-rs to fetch arbitrary URLs. This issue has been patched in version 0.19.16.
AI-Powered Analysis
Technical Analysis
CVE-2026-29178 is a Server-Side Request Forgery (SSRF) vulnerability identified in Lemmy, a federated link aggregator and forum software. The vulnerability arises from Lemmy's dependency on the Rust-based activitypub_federation framework and its interaction with pict-rs, an image proxy service. Specifically, the GET /api/v4/image/{filename} endpoint accepts a file_type query parameter that is improperly sanitized, allowing attackers to inject arbitrary query parameters into internal requests made to pict-rs. Among these parameters is the proxy parameter, which instructs pict-rs to fetch arbitrary URLs. Because this endpoint is unauthenticated, an attacker can exploit this SSRF flaw remotely without any credentials or user interaction. The SSRF can be leveraged to access internal network resources, potentially bypassing firewall restrictions, or to cause denial of service by forcing the server to make numerous or malicious requests. The vulnerability affects all Lemmy versions prior to 0.19.16, where the issue has been patched. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction required, with high impact on integrity but no impact on confidentiality or availability. No known exploits have been reported in the wild as of the publication date. The root cause is insufficient input validation and unsafe parameter forwarding to an internal proxy service.
Potential Impact
The SSRF vulnerability in Lemmy can have significant impacts on organizations running vulnerable instances, especially those exposing the affected endpoint to the internet. Attackers can exploit this flaw to make arbitrary HTTP requests from the Lemmy server, potentially accessing internal services that are otherwise inaccessible externally, such as internal APIs, metadata services in cloud environments, or administrative interfaces. This can lead to information disclosure, unauthorized internal network reconnaissance, and lateral movement within the network. Additionally, attackers could use the SSRF to perform denial of service attacks by overwhelming internal or external resources. Since Lemmy is a federated platform used by communities worldwide, exploitation could disrupt communication and content sharing. The unauthenticated nature of the vulnerability increases the risk, as no credentials are needed to exploit it. Although no active exploitation has been reported, the high CVSS score and ease of exploitation make it a critical risk for organizations relying on Lemmy for federated social networking.
Mitigation Recommendations
The primary mitigation is to upgrade Lemmy to version 0.19.16 or later, where the SSRF vulnerability has been patched. Organizations should prioritize this update to eliminate the unsafe parameter injection. Additionally, administrators should implement network-level controls to restrict outbound HTTP requests from the Lemmy server to only trusted destinations, reducing the impact of potential SSRF exploitation. Employing web application firewalls (WAFs) with rules to detect and block suspicious query parameter patterns targeting the /api/v4/image/ endpoint can provide an additional layer of defense. Monitoring server logs for unusual outbound requests or spikes in traffic to internal services can help detect exploitation attempts. If upgrading immediately is not feasible, temporarily disabling or restricting access to the vulnerable endpoint can reduce exposure. Finally, conducting internal network segmentation and limiting the Lemmy server's access to sensitive internal resources will minimize the potential damage from SSRF attacks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-04T14:44:00.713Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69ab19e8c48b3f10ffbbf2b1
Added to database: 3/6/2026, 6:16:08 PM
Last enriched: 3/6/2026, 6:30:21 PM
Last updated: 3/7/2026, 8:13:00 AM
Views: 8
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.
Need more coverage?
Upgrade to Pro Console in Console -> Billing 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.