CVE-2025-62166 FreshRSS has an IDOR which allows for viewing feeds of any user and leaking tokens
Attackers can view private feeds and leak tokens of any user by bypassing authentication restrictions in FreshRSS.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-62166?
CVE-2025-62166 is a high-severity missing authorization vulnerability in FreshRSS, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
FreshRSS is a free, self-hostable RSS aggregator. Prior 1.28.0, a bug in the auth logic related to master authentication tokens, this restriction is bypassed. Usually only the default user's feed should be viewable if anonymous viewing is enabled, and feeds of other users should be private. This vulnerability is fixed in 1.28.0.
Which versions are affected by CVE-2025-62166?
It affects 1 product.
Products include Freshrss Freshrss.
How do I fix CVE-2025-62166?
No fix has been published for CVE-2025-62166 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2025-62166 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62166 exists.
Other vulnerabilities in FreshRSS
- CVE-2025-54875 FreshRSS: Unauthorized creation of admin user when registration is enabled
- CVE-2025-54592 FreshRSS has Incomplete Session Termination on Logout
- CVE-2025-54591 FreshRSS: Unauthenticated users can view default user's information
- CVE-2025-58173 FreshRSS vulnerable to authenticated RCE via path traversal inside include()
- CVE-2025-54593 FreshRSS is vulnerable to RCE attacks by authenticated admin
Sources
Also known as GHSA-w743-fg6g-mhwh.