CVE-2025-46341: Privilege escalation via SSRF when using HTTP auth
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-46341?
CVE-2025-46341 has been classified as a high severity vulnerability.
How do I fix CVE-2025-46341?
To fix CVE-2025-46341, update FreshRSS to version 1.26.2 or later.
What impact does CVE-2025-46341 have on FreshRSS users?
CVE-2025-46341 allows attackers to impersonate any user through HTTP authentication vulnerabilities.
Which versions of FreshRSS are affected by CVE-2025-46341?
FreshRSS versions prior to 1.26.2 are vulnerable to CVE-2025-46341.
What headers are involved in the exploitation of CVE-2025-46341?
The exploitation of CVE-2025-46341 can occur through the 'Remote-User' and 'X-WebAuth-User' headers.