# CVE-2025-68402: FreshRSS has an authentication bypass due to truncated bcrypt hash [edge branch]

> Attackers can bypass authentication in FreshRSS edge branch due to bcrypt hash truncation, allowing unauthorized account access.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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-pcq9-mq6m-mvmp

## What is CVE-2025-68402?

CVE-2025-68402 is a high-severity authentication bypass 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. From 57e1a37 - 00f2f04, the lengths of the nonce was changed from 40 chars to 64. password_verify() is currently being called with a constructed string (SHA-256 nonce + part of a bcrypt hash) instead of the raw user password. Due to bcrypt’s 72-byte input truncation, this causes password verification to succeed even when the user enters an incorrect password. This vulnerability is fixed in 1.27.2-dev (476e57b). The issue was only present in the edge branch and never in a stable release.

Weakness: CWE-287 (Improper Authentication)

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


## How do I fix CVE-2025-68402?

No fix has been published for CVE-2025-68402 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-68402 being exploited?

There is no known exploitation of CVE-2025-68402 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68402 is a high-severity authentication bypass 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: There is no known exploitation of CVE-2025-68402 in the wild and no public exploit code.

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-68402/ (Markdown: https://insights.sbomify.com/CVE-2025-68402/index.md)
```

## Sources

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

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