Account access via bcrypt input truncation
Published Mar 9, 2026 · Updated Mar 9, 2026
Authentication bypass in FreshRSS 1.27.2-dev edge builds allows remote attackers to access existing accounts with any password. FreshRSS_FormAuth::checkCredentials passes a 64-character SHA-256 nonce before a bcrypt-derived hash to password_verify(), so bcrypt's 72-byte limit discards password-dependent bytes. The flaw affects only edge commits 57e1a37 through 00f2f04; exploitation requires a valid username and grants that account's access.
Summary
What happened
Authentication bypass in FreshRSS 1.27.2-dev edge builds allows remote attackers to access existing accounts with any password. FreshRSS_FormAuth::checkCredentials passes a 64-character SHA-256 nonce before a bcrypt-derived hash to password_verify(), so bcrypt's 72-byte limit discards password-dependent bytes. The flaw affects only edge commits 57e1a37 through 00f2f04; exploitation requires a valid username and grants that account's access.
The record
- CVE
- CVE-2025-68402
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- FreshRSS
- Product
- FreshRSS
- Classifications
- CWE-287, 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=< 476e57b04646416e24e24c56133c9fadf9e52b95
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.
Public exploit references
- GitHub advisory any-password login proof of conceptproof 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