Miniflux has an Open Redirect via protocol-relative redirect_url

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-67713: 0.22% estimated exploitation activity in the next 30 days; percentile 12.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary redirecturl is treated as safe when url.Parse(...).IsAbs() is false. Protocol-relative URLs like //ikotaslabs.com have an empty scheme and pass that check, allowing post-login redirects to attacker-controlled sites. Details - url.Parse("//ikotaslabs.com") = empty Scheme, Host="ikotaslabs.com". - IsAbs() returns false for //ikotaslabs.com, so the code treats it as allowed. - Browser resolves //ikotaslabs.com to current-origin scheme (e.g. https://ikotaslabs.com), enabling phishing flows after login. PoC 1. Send or visit: http://localhost/login?redirecturl=//ikotaslabs.com 2. Complete normal login flow. 3. After login the app redirects to https://ikotaslabs.com (or http:// depending on origin). Acknowledgements This vulnerability was discovered using the automated vulnerability analysis tools VulScribe and PwnML. The research and tool development were conducted with support from the MITOU Advanced Program (未踏アドバンスト事業), implemented by the Information-technology Promotion Agency…

Published by the source

10 Dec 2025, 17:18 UTC

Last modified by the source

2 Feb 2026, 16:29 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wqv2-4wpg-8hc9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67713

Advisory: Miniflux has an Open Redirect via protocol-relative redirect_url
IDs: CVE-2025-67713, GHSA-wqv2-4wpg-8hc9
Record: https://patchnext.com/advisories/cve-2025-67713 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: miniflux.app/v2 2.2.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go miniflux.app/v2: affected <= 2.2.14; fixed in 2.2.15

## Suggested inspection (read-only)
- Go miniflux.app/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on miniflux.app/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wqv2-4wpg-8hc9 (GitHub-reviewed advisory GHSA-wqv2-4wpg-8hc9 lists affected ranges: Go miniflux.app/v2 >=0 <=2.2.14)

Commands are suggestions: review each one before running it.