# Lemmy has unauthenticated SSRF via file_type query parameter injection in image endpoint

Advisory record · `GHSA-jvxv-2jjp-jxc3`

- **Identifiers:** `GHSA-jvxv-2jjp-jxc3` · `CVE-2026-29178`
- **State:** Confirmed
- **Severity:** CVSS 7.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 4 Mar 2026
- **Updated:** 6 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Mar 2026, 20:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `lemmy_routes` (crates.io): affected `<0.19.16`; fixed in `0.19.16`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Lemmy's lemmy_routes crate, versions before 0.19.16, is vulnerable to server-side request forgery through the unauthenticated GET /api/v4/image/{filename} endpoint. The file_type query parameter is inserted into the internal request to pict-rs without validation, so an attacker can inject a proxy parameter and make pict-rs fetch arbitrary URLs, potentially reaching cloud metadata services or internal services and returning the response to the attacker. Upgrade lemmy_routes to version 0.19.16 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 21st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:19 UTC: First seen by agentprime
- 31 Oct 2026, 15:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jvxv-2jjp-jxc3)

## Sources

- [GitHub Advisory Database: GHSA-jvxv-2jjp-jxc3](https://github.com/advisories/GHSA-jvxv-2jjp-jxc3)
- [OSV: GHSA-jvxv-2jjp-jxc3](https://osv.dev/vulnerability/GHSA-jvxv-2jjp-jxc3)
- <https://github.com/LemmyNet/lemmy/security/advisories/GHSA-jvxv-2jjp-jxc3>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-29178>
- <https://github.com/LemmyNet/lemmy/commit/f47a03f56d1797bceab5f34b6f624c91cecd5871>
- <https://github.com/LemmyNet/lemmy>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jvxv-2jjp-jxc3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jvxv-2jjp-jxc3/>. Everything for agents: <https://agentprime.io/llms.txt>.