Unauthenticated account enumeration via password-check timing
Published Aug 29, 2026 · Updated Aug 29, 2026
Observable timing discrepancy in Cockpit CMS before 2.14.1 allows remote attackers to enumerate accounts through the auth check endpoint. The Auth controller calls password_verify only when a submitted account exists, while unknown accounts return immediately without equivalent bcrypt work. No authentication or user interaction is required, but reliable enumeration depends on comparing response times across multiple requests.
Summary
What happened
Observable timing discrepancy in Cockpit CMS before 2.14.1 allows remote attackers to enumerate accounts through the auth check endpoint. The Auth controller calls password_verify only when a submitted account exists, while unknown accounts return immediately without equivalent bcrypt work. No authentication or user interaction is required, but reliable enumeration depends on comparing response times across multiple requests.
The record
- CVE
- CVE-2026-82449
- Published
- Aug 29, 2026
- Updated
- Aug 29, 2026
- Vendor
- Cockpit HQ
- Product
- Cockpit CMS
- Classifications
- CWE-208, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2026CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=0 <2.14.1
What conditions does exploitation require?
What is affected?
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
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