# CVE-2026-21885: Miniflux Media Proxy SSRF via /proxy endpoint allows access to internal network resources

> An authenticated user can exploit the media proxy to perform Server-Side Request Forgery, accessing internal network resources and metadata endpoints.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** DEBIAN-CVE-2026-21885, GHSA-xwh2-742g-w3wp, GO-2026-4287, UBUNTU-CVE-2026-21885

## What is CVE-2026-21885?

CVE-2026-21885 is a medium-severity server-side request forgery vulnerability in miniflux v2, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Miniflux 2 is an open source feed reader. Prior to version 2.2.16, Miniflux's media proxy endpoint (`GET /proxy/{encodedDigest}/{encodedURL}`) can be abused to perform Server-Side Request Forgery (SSRF). An authenticated user can cause Miniflux to generate a signed proxy URL for attacker-chosen media URLs embedded in feed entry content, including internal addresses (e.g., localhost, private RFC1918 ranges, or link-local metadata endpoints). Requesting the resulting `/proxy/...` URL makes Miniflux fetch and return the internal response. Version 2.2.16 fixes the issue.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-21885?

4 open source packages ship an affected version, including miniflux.app/v2 and miniflux.app. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `miniflux.app/v2` | Go | All versions | 2.2.16 |
| `miniflux.app/v2` | Go | All versions | 2.2.16 |
| `miniflux.app/v2` | Go | All versions | 2.2.16 |
| `miniflux.app` | Go | All versions | None |

Products: Miniflux Project Miniflux.

## How do I fix CVE-2026-21885?

Upgrade miniflux.app/v2 to 2.2.16 or later.

## Is CVE-2026-21885 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21885 exists.

## Other vulnerabilities in miniflux v2

- [CVE-2023-27591](https://insights.sbomify.com/CVE-2023-27591/): Unauthenticated Miniflux user can bypass allowed networks check to obtain Prometheus metrics (high 7.5)
- [CVE-2025-67713](https://insights.sbomify.com/CVE-2025-67713/): Miniflux 2 has an Open Redirect via protocol-relative `redirect_url` (medium 5.3)
- [CVE-2023-27592](https://insights.sbomify.com/CVE-2023-27592/): Stored XSS in Miniflux when opening a broken image due to unescaped ServerError in proxy handler (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21885 and fix it if it is affected.

What it is: CVE-2026-21885 is a medium-severity server-side request forgery vulnerability in miniflux v2, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21885 exists.

Affected packages and fixed versions:
- miniflux.app/v2 (Go): affected all versions; fixed in 2.2.16
- miniflux.app/v2 (Go): affected all versions; fixed in 2.2.16
- miniflux.app/v2 (Go): affected all versions; fixed in 2.2.16
- miniflux.app (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-21885/ (Markdown: https://insights.sbomify.com/CVE-2026-21885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-21885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21885
- OSV: https://osv.dev/vulnerability/CVE-2026-21885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-21885/
Summaries are generated and may contain mistakes; the official description above is the record.