# CVE-2026-76235: Cockpit-ws: cockpit: cockpit-ws: unauthenticated remote memory leak via cockpitlang cookie in send_login_html

> Unauthenticated attackers can exhaust host memory via a leak in the login page handler, causing denial of service in Cockpit web console.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-76235, GHSA-hwfh-3wjq-8p68, MGASA-2026-0408, OESA-2026-3578, UBUNTU-CVE-2026-76235

## What is CVE-2026-76235?

CVE-2026-76235 is a high-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A memory leak flaw was found in cockpit-ws. The login page handler leaks a heap allocation on every unauthenticated request that carries a CockpitLang cookie, allowing a remote unauthenticated attacker to exhaust memory on the host and cause a denial of service.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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


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

Apply the vendor's patch.

## Is CVE-2026-76235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76235 is a high-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 19 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-76235 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-76235/ (Markdown: https://insights.sbomify.com/CVE-2026-76235/index.md)
```

## Sources

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

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