Quick answers
- Is CVE-2026-82449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82449 being exploited in the wild.
- How severe is CVE-2026-82449?
- Medium severity, with a CVSS score of 5.3, published 29 August 2026.
- Which products and versions are affected?
- Cockpit-HQ Cockpit CMS before 2.14.1.
- Is there a fix for CVE-2026-82449?
- A patch was published on 2026: Fixed in version 2.14.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82449 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82449?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The auth check endpoint in Cockpit CMS before version 2.14.1 is vulnerable to account enumeration via timing side-channel analysis. The root cause is inconsistent response times during password verification: legitimate accounts trigger computationally expensive bcrypt password verification, while non-existent accounts return immediately without verification, creating a measurable timing discrepancy. An attacker can send multiple authentication requests with different usernames and measure response latency to determine which accounts exist, requiring no authentication and only network reachability to the auth endpoint. By correlating timing patterns across requests, attackers can build a list of valid usernames for subsequent brute-force or credential-stuffing attacks. The vulnerability was patched in version 2.14.1.
Affected products
- Cockpit-HQ Cockpit CMS before 2.14.1
Timeline
- 2026-08-29: disclosed
- 2026: patched: Fixed in version 2.14.1