# CVE-2026-82449: Cockpit CMS before 2.14.1 Account Enumeration via Auth Timing

> Attackers can enumerate valid user accounts in Cockpit CMS by analyzing response time differences during authentication attempts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-x5j5-9mrv-74fr

## What is CVE-2026-82449?

CVE-2026-82449 is a medium-severity vulnerability in cockpit-hq cockpit, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cockpit CMS before 2.14.1 contains an account enumeration vulnerability in the auth check endpoint due to timing discrepancies in password verification. Attackers can measure response times across multiple requests to determine which accounts exist by observing that existing accounts trigger bcrypt verification while non-existent accounts return immediately.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2026-82449?


## How do I fix CVE-2026-82449?

No fix has been published for CVE-2026-82449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82449 being exploited?

There is no known exploitation of CVE-2026-82449 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82449 and fix it if it is affected.

What it is: CVE-2026-82449 is a medium-severity vulnerability in cockpit-hq cockpit, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82449 in the wild and no public exploit code.

Affected product: cockpit-hq cockpit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82449/ (Markdown: https://insights.sbomify.com/CVE-2026-82449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82449
- OSV: https://osv.dev/vulnerability/CVE-2026-82449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82449/
Summaries are generated and may contain mistakes; the official description above is the record.