VulnerabilityPublished 8 Jan 2026

CVE-2026-21885: miniflux v2 · Server-Side Request Forgery (SSRF)

Affects miniflux v2Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.16 when convenient.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.2.16

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade v2 and miniflux/v2 to 2.2.16.

Affected software

Product	Affected	Fixed in
minifluxv2	Affected <2.2.16	Fixed in 2.2.16
GitHubminiflux/v2`pkg:github/miniflux/v2`Other threats	Affected <2.2.16	Fixed in 2.2.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade Miniflux to version 2.2.16 or later, where this SSRF vulnerability is fixed. Until the upgrade is applied, restrict access to the media proxy endpoint to trusted users only and monitor usage for suspicious activity. Implement network-level controls to limit Miniflux server outbound requests to only necessary external addresses, blocking access to internal IP ranges and cloud metadata endpoints. Employ strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. Conduct regular audits of user accounts and permissions to ensure only authorized users have access to Miniflux. Additionally, consider deploying web application firewalls (WAFs) with rules to detect and block SSRF patterns targeting proxy endpoints. Monitor logs for unusual proxy URL generation or access patterns that may indicate exploitation attempts. Finally, educate users about the risks of credential phishing and enforce robust password policies to minimize the risk of unauthorized access.

Description

Miniflux 2 is an open source feed reader. Prior to version 2.2.16, Miniflux's media proxy endpoint (`GET /proxy/{encodedDigest}/{encodedURL}`) can be abused to perform Server-Side Request Forgery (SSRF). An authenticated user can cause Miniflux to generate a signed proxy URL for attacker-chosen media URLs embedded in feed entry content, including internal addresses (e.g., localhost, private RFC1918 ranges, or link-local metadata endpoints). Requesting the resulting `/proxy/...` URL makes Miniflux fetch and return the internal response. Version 2.2.16 fixes the issue.

Impact

For European organizations using vulnerable versions of Miniflux, this SSRF vulnerability poses a significant risk of internal network reconnaissance and data exposure. Attackers with valid user credentials can exploit the proxy endpoint to access internal services, including sensitive metadata endpoints in cloud environments (e.g., AWS, Azure, GCP). This can lead to leakage of confidential information such as internal IP addresses, service configurations, or credentials stored in metadata services. Although the vulnerability does not directly impact data integrity or system availability, the confidentiality breach can facilitate lateral movement, privilege escalation, or targeted attacks within the network. Organizations relying on Miniflux for internal or external feed aggregation should consider the risk of exposing internal infrastructure details and the potential for attackers to bypass perimeter defenses. The impact is heightened in environments with sensitive internal services or cloud deployments where metadata endpoints are critical. The requirement for authentication limits exposure to insiders or compromised accounts, but this does not eliminate the risk, especially in environments with weak credential management or phishing threats.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/miniflux/v2/security/advisories/GHSA-xwh2-742g-w3wp (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jan 2026, 14:20 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats