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

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-w743-fg6g-mhwh

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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-62166?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2025-54875/): FreshRSS: Unauthorized creation of admin user when registration is enabled (critical 9.8)
- [CVE-2025-54592](https://insights.sbomify.com/CVE-2025-54592/): FreshRSS has Incomplete Session Termination on Logout (high 8.8)
- [CVE-2025-54591](https://insights.sbomify.com/CVE-2025-54591/): FreshRSS: Unauthenticated users can view default user's information (high 7.5)
- [CVE-2025-58173](https://insights.sbomify.com/CVE-2025-58173/): FreshRSS vulnerable to authenticated RCE via path traversal inside include() (high 7.4)
- [CVE-2025-54593](https://insights.sbomify.com/CVE-2025-54593/): FreshRSS is vulnerable to RCE attacks by authenticated admin (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62166 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62166 exists.

Affected product: FreshRSS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62166/ (Markdown: https://insights.sbomify.com/CVE-2025-62166/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62166
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62166
- OSV: https://osv.dev/vulnerability/CVE-2025-62166

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62166/
Summaries are generated and may contain mistakes; the official description above is the record.