Skip to main content
Vulnerability Database/CVE-2026-108735

CVE-2026-108735: Miniflux SSRF Vulnerability

CVE-2026-108735 is an SSRF vulnerability in Miniflux versions 2.3.0 through 2.3.3 that lets authenticated users access internal networks. This article covers technical details, affected versions, security impact, and remediation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-108735 Overview

CVE-2026-108735 is a Server-Side Request Forgery (SSRF) vulnerability [CWE-918] in Miniflux 2, an open-source feed reader. Versions 2.3.0 through 2.3.3 allow authenticated users to abuse a feed's proxy_url setting to force the Miniflux server to issue requests to internal or loopback addresses. The flaw bypasses the FETCHER_ALLOW_PRIVATE_NETWORKS safeguard, which normally blocks requests to private network ranges. Attackers can probe internal ports and send proxy-style requests to services that are not exposed on the public internet.

Critical Impact

Authenticated attackers can pivot from a Miniflux instance into internal networks, exposing metadata endpoints, administrative panels, and other non-public services.

Affected Products

  • Miniflux 2.3.0
  • Miniflux 2.3.1 through 2.3.2
  • Miniflux 2.3.3

Discovery Timeline

  • 2026-10-11 - CVE-2026-108735 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-108735

Vulnerability Analysis

Miniflux allows each feed to define a proxy_url used when fetching content. The request builder honors this value without validating it against the same private-network restrictions applied to the primary feed URL. As a result, an authenticated user who can add or edit a feed can set proxy_url to a loopback or RFC1918 address and cause the Miniflux backend to connect there.

Because the server initiates the connection, the attacker gains the ability to probe internal infrastructure from the trust boundary of the Miniflux host. This includes cloud metadata services, internal APIs, databases, and administrative interfaces reachable from the server. The relevant logic can be reviewed in the Miniflux Request Builder code and the Miniflux URL utility code.

Root Cause

The FETCHER_ALLOW_PRIVATE_NETWORKS guard is enforced on the feed target URL but not on the per-feed proxy_url. Validation logic in the URL helper does not reject private, loopback, or link-local destinations supplied through the proxy field. The proxy path effectively creates a second request destination that was never routed through the same safety check.

Attack Vector

Exploitation requires an authenticated account with permission to create or modify a feed. The attacker sets proxy_url to a target such as http://127.0.0.1:PORT or an internal hostname. When Miniflux refreshes the feed, it sends a proxy-style HTTP request to the specified address. Response behavior, timing, and error messages let the attacker enumerate open ports and reachable services. Additional detail is available in the VulnCheck SSRF Advisory for Miniflux and the HackMD Miniflux Proxy Analysis.

// No verified exploit code is published for this CVE.
// See VulnCheck advisory and HackMD analysis for technical details.

Detection Methods for CVE-2026-108735

Indicators of Compromise

  • Feed records containing a proxy_url value pointing to loopback (127.0.0.0/8, ::1), link-local (169.254.0.0/16), or RFC1918 ranges.
  • Outbound connections from the Miniflux process to internal addresses that do not host RSS or Atom content.
  • Unusual HTTP error patterns in Miniflux logs tied to feed refresh operations targeting internal hosts.

Detection Strategies

  • Audit the Miniflux database feeds table for non-public proxy_url entries and flag any that resolve to internal IP space.
  • Correlate feed refresh timestamps with egress connections initiated by the Miniflux service to detect probing patterns.
  • Alert on repeated connection attempts from the Miniflux host to varied internal ports, which indicates port scanning via SSRF.

Monitoring Recommendations

  • Capture egress network telemetry for the Miniflux host and compare destinations against an allowlist of expected feed providers.
  • Monitor cloud instance metadata endpoints (for example, 169.254.169.254) for access attempts originating from the Miniflux workload.
  • Record all feed create and update operations with the authenticated user identity for forensic review.

How to Mitigate CVE-2026-108735

Immediate Actions Required

  • Upgrade Miniflux to a fixed release once published by the maintainers; track the Miniflux GitHub Repository for release notes.
  • Restrict account creation on public Miniflux instances and review existing user accounts for untrusted principals.
  • Inspect existing feeds and remove any with proxy_url values resolving to internal, loopback, or metadata addresses.

Patch Information

No fixed version is listed in the enriched NVD data at the time of writing. Monitor the Miniflux GitHub Repository and the VulnCheck SSRF Advisory for Miniflux for a patched release addressing the per-feed proxy_url validation gap.

Workarounds

  • Deploy Miniflux behind an egress proxy or firewall that denies connections to RFC1918, loopback, link-local, and cloud metadata ranges.
  • Run Miniflux in a network segment isolated from internal services and cloud metadata endpoints.
  • Disable or restrict per-feed proxy configuration if your deployment does not require it, limiting proxy settings to administrators only.
bash
# Example iptables egress restriction for the Miniflux host
iptables -A OUTPUT -d 127.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 10.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 172.16.0.0/12 -j REJECT
iptables -A OUTPUT -d 192.168.0.0/16 -j REJECT
iptables -A OUTPUT -d 169.254.0.0/16 -j REJECT

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.