Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-21885: CWE-918: Server-Side Request Forgery (SSRF) in miniflux v2

0
Medium
VulnerabilityCVE-2026-21885cvecve-2026-21885cwe-918
Published: Thu Jan 08 2026 (01/08/2026, 13:57:25 UTC)
Source: CVE Database V5
Vendor/Project: miniflux
Product: v2

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.

AI-Powered Analysis

AILast updated: 01/08/2026, 14:20:39 UTC

Technical Analysis

CVE-2026-21885 is a Server-Side Request Forgery (SSRF) vulnerability identified in Miniflux version 2, an open-source feed reader. The vulnerability exists in the media proxy endpoint (`GET /proxy/{encodedDigest}/{encodedURL}`) prior to version 2.2.16. Authenticated users can exploit this endpoint to generate signed proxy URLs that cause the Miniflux server to fetch arbitrary URLs chosen by the attacker. This includes URLs pointing to internal network resources such as localhost, private IP ranges defined by RFC1918, or link-local metadata endpoints often used in cloud environments. By requesting the generated proxy URL, the attacker can retrieve responses from these internal resources, potentially exposing sensitive information or internal services that are not meant to be publicly accessible. The vulnerability requires authentication but no additional user interaction, making it a direct threat once credentials are obtained. The CVSS 3.1 base score is 6.5, indicating a medium severity with a high impact on confidentiality but no impact on integrity or availability. The issue was addressed and fixed in Miniflux version 2.2.16. There are no known exploits in the wild at the time of publication. The vulnerability stems from inadequate validation and filtering of URLs passed to the proxy endpoint, allowing SSRF attacks that can bypass network segmentation and firewall protections. This can lead to information disclosure from internal systems and cloud metadata services, which can be leveraged for further attacks.

Potential 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.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T17:24:36.928Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695fb9abc901b06321f2a5dd

Added to database: 1/8/2026, 2:05:31 PM

Last enriched: 1/8/2026, 2:20:39 PM

Last updated: 1/9/2026, 12:45:43 AM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats