Authenticated account lockout via crafted server request
Published Apr 28, 2026 · Updated Apr 28, 2026
Account-lockout abuse in Ercom Cryptobox server before 4.38.0 and 4.40.175 allows authenticated users to prevent other users from logging in. Ercom identifies a specially crafted request and duplicate-identifier handling but does not disclose the affected endpoint or the operation that associates the request with another account. Low-privileged network access is required, and the reported consequence is limited to the targeted account's availability.
Summary
What happened
Account-lockout abuse in Ercom Cryptobox server before 4.38.0 and 4.40.175 allows authenticated users to prevent other users from logging in. Ercom identifies a specially crafted request and duplicate-identifier handling but does not disclose the affected endpoint or the operation that associates the request with another account. Low-privileged network access is required, and the reported consequence is limited to the targeted account's availability.
The record
- CVE
- CVE-2026-5794
- Published
- Apr 28, 2026
- Updated
- Apr 28, 2026
- Vendor
- Ercom
- Product
- Cryptobox
- Classifications
- CWE-694, CAPEC-2, T1531
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=4.37.237 <4.38.0
- Affected versionversion=4.40.175
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
No public exploit references are available in this record.
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