Quick answers
- Is CVE-2026-109379 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109379 being exploited in the wild.
- How severe is CVE-2026-109379?
- Medium severity, with a CVSS score of 5.3, published 12 October 2026.
- Which products and versions are affected?
- Cockpit CMS 2.14.1.
- Is there a fix for CVE-2026-109379?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-109379 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109379?
- Check whether you run Cockpit CMS at an affected version. 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
A timing discrepancy vulnerability in the /auth/check endpoint allows observable differences in response time based on whether an account exists. Existing accounts trigger two bcrypt operations while non-existent accounts trigger one, enabling unauthenticated attackers to enumerate valid usernames and email addresses through timing analysis. No authentication is required to exploit this vulnerability.
Affected products
- Cockpit Cockpit CMS 2.14.1
Timeline
- 2026-10-12: disclosed