Server-side Request Forgery (SSRF) Affecting miniflux.app/v2/internal/ui package, versions <2.2.16
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-MINIFLUXAPPV2INTERNALUI-14912647
- published12 Jan 2026
- disclosed8 Jan 2026
- crediteclipse07077
Introduced: 8 Jan 2026
CVE-2026-21885 Â (opens in a new tab)How to fix?
Upgrade miniflux.app/v2/internal/ui to version 2.2.16 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the proxy endpoint. An attacker can access internal network resources by crafting requests to internal addresses through authenticated sessions.
PoC
- Run Miniflux 2.2.15 with default configuration (media proxy enabled by default: MEDIA_PROXY_MODE=http-only).
- Log in with any normal user account.
- Subscribe to a feed you control that contains an entry with an image URL pointing to an internal address reachable from the Miniflux server, e.g.:
<img src="http://<internal-target>/secret">
(Note: must be reachable from the Miniflux process/network; in containerized setups, 127.0.0.1 may not refer to the host.) Open the entry and locate the rewritten media proxy URL (/proxy//) in the rendered HTML/page source.
- Request the /proxy/... URL.
- Expected (vulnerable): Miniflux fetches the internal URL and returns the internal response (SSRF).