Miniflux 2: Open Redirect Bypass

Answer in brief

CVE-2026-55185 records a Medium severity vulnerability in Miniflux 2: Open Redirect Bypass. The current sources do not mark it as known exploited. The current feed maps miniflux/v2 (generic), miniflux.app/v2 (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 21, 2026Updated Aug 21, 2026Source checked Aug 21, 2026First seen by HOL Jun 19, 2026Material review Aug 21, 2026

Upstream Advisory

Key facts

Risk: Medium
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps miniflux/v2 (generic), miniflux.app/v2 (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
miniflux/v2generic	< 2.3.1	Not reported
miniflux.app/v2go	<=2.3.0	2.3.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for miniflux/v2, miniflux.app/v2.
Review the reported fix. Update miniflux.app/v2 to 2.3.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 19, 2026

Sources and claim methodology

Upstream source description

Miniflux 2 is an open source feed reader. Prior to 2.3.1, IsRelativePath in internal/urllib/url.go accepts redirect targets containing backslashes because Go URL parsing treats them as path characters. Browser backslash normalization converts them to forward slashes. An unauthenticated attacker can provide such a redirect_url value to the login flow, bypass the relative-path and host checks, and redirect a victim to an attacker-controlled external site. This issue is fixed in version 2.3.1.

Quoted source text, attributed separately from HOL analysis.