# CVE-2026-68762: Denial of service in Ktor

> Attackers can cause a denial of service in JetBrains Ktor applications by exploiting WebSocket decompression flaws.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-cw22-f535-mjjw

## What is CVE-2026-68762?

CVE-2026-68762 is a medium-severity denial of service vulnerability in JetBrains Ktor, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JetBrains Ktor before 3.4.1 potential DoS attack via WebSocket decompression was possible

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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


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

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

## Is CVE-2026-68762 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68762 is a medium-severity denial of service vulnerability in JetBrains Ktor, published on 17 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-68762 in the wild and no public exploit code.

Affected product: JetBrains Ktor. 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-68762/ (Markdown: https://insights.sbomify.com/CVE-2026-68762/index.md)
```

## Sources

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

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