Username enumeration via inconsistent recovery error punctuation
Published Jan 3, 2026 · Updated Jan 3, 2026
Observable response discrepancy in AnythingLLM allows remote attackers to enumerate usernames through password recovery requests. The recoverAccount function returns “Invalid recovery codes” for some existing-user failures but adds a period when the username does not exist. No authentication or user interaction is required; disclosure is limited to whether a submitted username exists and supports targeted follow-on attacks.
Summary
What happened
Observable response discrepancy in AnythingLLM allows remote attackers to enumerate usernames through password recovery requests. The recoverAccount function returns “Invalid recovery codes” for some existing-user failures but adds a period when the username does not exist. No authentication or user interaction is required; disclosure is limited to whether a submitted username exists and supports targeted follow-on attacks.
The record
- CVE
- CVE-2026-21484
- Published
- Jan 3, 2026
- Updated
- Jan 3, 2026
- Vendor
- Mintplex Labs
- Product
- AnythingLLM
- Classifications
- CWE-204, CWE-203, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2026CVE publishedPublication date reported by the CVE source.
- Jan 3, 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=< e287fab56089cf8fcea9ba579a3ecdeca0daa313
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
- GitHub advisory password-recovery PoCproof 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