CVE-2026-55185: miniflux v2 · Open Redirect
Affects miniflux v2Source CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.3.1 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade v2 and miniflux/v2 to 2.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| minifluxv2 | Affected
| Fixed in
|
GitHubminiflux/v2pkg:github/miniflux/v2Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Miniflux to version 2.3.1 or later, where this open redirect vulnerability is fixed. No other mitigation is required as the fix is official and addresses the issue directly.
Description
Miniflux v2 before version 2.3.1 contains an open redirect vulnerability due to improper handling of redirect URLs with backslashes. This allows an unauthenticated attacker to bypass relative-path and host checks in the login flow and redirect users to attacker-controlled external sites. The issue is fixed in version 2.3.1.