CVE-2025-46341: FreshRSS · Server-Side Request Forgery (SSRF)
Affects FreshRSSSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 1.26.2 soon.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.26.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Jun 2025
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.
What to do
Upgrade freshrss/FreshRSS to 1.26.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfreshrss/FreshRSSpkg:github/freshrss/FreshRSSOther threats | Affected
| Fixed in
|
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 all FreshRSS instances to version 1.26.2 or later to apply the official patch addressing CVE-2025-46341. For those unable to upgrade promptly, it is critical to review and restrict access to the FreshRSS instance, ensuring that only trusted IP addresses can reach the service, thereby reducing the attack surface. Additionally, organizations should consider migrating authentication mechanisms from HTTP auth via reverse proxy to more secure methods such as OpenID Connect (OIDC), which mitigates the privilege escalation vector. Implement strict validation and sanitization of HTTP headers like 'Remote-User' and 'X-WebAuth-User' at the proxy or application level to prevent header spoofing. Monitoring and logging of unusual access patterns or header manipulations should be enhanced to detect potential exploitation attempts. Network segmentation should be enforced to limit the ability of an attacker to reach internal services via SSRF. Finally, conduct security awareness and training for administrators to recognize and respond to SSRF-related threats and ensure that CSRF tokens and other security tokens are handled securely to prevent scraping or leakage.
Description
FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, when the server is using HTTP auth via reverse proxy, it's possible to impersonate any user either via the `Remote-User` header or the `X-WebAuth-User` header by making specially crafted requests via the add feed functionality and obtaining the CSRF token via XPath scraping. The attacker has to know the IP address of the proxied FreshRSS instance and the admin's username, while also having an account on the instance. An attacker can send specially crafted requests in order to gain unauthorized access to internal services. This can also lead to privilege escalation like in the demonstrated scenario, although users that have setup OIDC are not affected by privilege escalation. Version 1.26.2 contains a patch for the issue.