Quick answers
- Is CVE-2026-55185 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55185 being exploited in the wild.
- How severe is CVE-2026-55185?
- Medium severity, with a CVSS score of 4, published 21 August 2026.
- Which products and versions are affected?
- miniflux.app (Go) SEMVER:introduced=0; miniflux.app/v2 (Go) <= 2.3.0, SEMVER:introduced=0,fixed=2.3.1; Miniflux <= 2.3.0.
- Is there a fix for CVE-2026-55185?
- Yes. miniflux.app/v2 (Go): upgrade to 2.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55185 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55185?
- Check whether you run miniflux.app (Go), miniflux.app/v2 (Go) or Miniflux at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- miniflux.app/v2 (Go): upgrade to 2.3.1 or later
go get miniflux.app/v2@v2.3.1
Technical details
An open redirect vulnerability exists in Miniflux v2 due to insufficient validation in the IsRelativePath function. While the application attempts to block absolute URLs and protocol-relative paths (e.g., //example.com), it fails to account for backslash characters that browsers automatically normalize. An attacker can use a payload like '/\example.com' to bypass the relative path check. The backend treats this as a relative path because it lacks a host or scheme, but modern browsers interpret the backslash as a forward slash, resulting in a redirection to an external domain. This can be exploited via the redirect_url parameter during login or other navigation events. The issue is fixed in version 2.3.1.
Affected products
- miniflux miniflux/v2 <= 2.3.0
Identifiers
- CVE-2026-55185
- GHSA-m999-j542-5w3r
- GO-2026-5500
Timeline
- 2026-06-18: disclosed
- 2026-06-19: advisory
- 2026-06-19: patched: Fixed in version 2.3.1