Unauthenticated feed and token disclosure via unvalidated token
Published Mar 9, 2026 · Updated Mar 9, 2026
Improper access control in FreshRSS before 1.28.0 allows remote attackers to read any user's feeds and master tokens over the network. FreshRSS_Auth::removeAccess() accepts any nonempty token parameter, changes context to the attacker-selected user, and leaves anonymous-capable actions reachable. Anonymous viewing must be enabled; the flaw exposes feed data, OPML credentials, and reusable master tokens but does not grant write access.
Summary
What happened
Improper access control in FreshRSS before 1.28.0 allows remote attackers to read any user's feeds and master tokens over the network. FreshRSS_Auth::removeAccess() accepts any nonempty token parameter, changes context to the attacker-selected user, and leaves anonymous-capable actions reachable. Anonymous viewing must be enabled; the flaw exposes feed data, OPML credentials, and reusable master tokens but does not grant write access.
The record
- CVE
- CVE-2025-62166
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- FreshRSS
- Product
- FreshRSS
- Classifications
- CWE-284, CWE-639, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.28.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-w743-fg6g-mhwh reproduction requestsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo