Email address enumeration via divergent login responses
Published Feb 27, 2026 · Updated Feb 27, 2026
Observable response discrepancy in Dify before 1.9.0 allows remote attackers to enumerate registered email addresses through the login API. POST /console/api/login returns a generic 401 response for an existing email with an incorrect password but a 400 account-not-found response for an unknown email. Unauthenticated network access is sufficient; brute-force protection limits repeated probes, and the direct consequence is disclosure of account existence.
Summary
What happened
Observable response discrepancy in Dify before 1.9.0 allows remote attackers to enumerate registered email addresses through the login API. POST /console/api/login returns a generic 401 response for an existing email with an incorrect password but a 400 account-not-found response for an unknown email. Unauthenticated network access is sufficient; brute-force protection limits repeated probes, and the direct consequence is disclosure of account existence.
The record
- CVE
- CVE-2026-28288
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- LangGenius
- Product
- Dify
- Classifications
- CWE-204, T1589.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 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.9.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
- Dify login-response differential 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