# CVE-2022-35838: HTTP V3 Denial of Service Vulnerability


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Sep 2022
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-cm5q-fcm3-4m7v

## What is CVE-2022-35838?

CVE-2022-35838 is a high-severity vulnerability in Microsoft Windows 11, published on 13 Sep 2022. 

### Official description

HTTP V3 Denial of Service Vulnerability

## Which versions are affected by CVE-2022-35838?

It affects 2 products.


Products: Microsoft Windows 11, Microsoft Windows Server 2022.

## How do I fix CVE-2022-35838?

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

## Is CVE-2022-35838 being exploited?

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

## Other vulnerabilities in Microsoft Windows 11

- [CVE-2022-35804](https://insights.sbomify.com/CVE-2022-35804/): SMB Client and Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-29133](https://insights.sbomify.com/CVE-2022-29133/): Windows Kernel Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2021-38672](https://insights.sbomify.com/CVE-2021-38672/): Windows Hyper-V Remote Code Execution Vulnerability (high 8.0)
- [CVE-2023-21768](https://insights.sbomify.com/CVE-2023-21768/): Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability (high 7.8)
- [CVE-2022-44710](https://insights.sbomify.com/CVE-2022-44710/): DirectX Graphics Kernel Elevation of Privilege Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35838 and fix it if it is affected.

What it is: CVE-2022-35838 is a high-severity vulnerability in Microsoft Windows 11, published on 13 Sep 2022. 
Exploitation: There is no known exploitation of CVE-2022-35838 in the wild and no public exploit code.

Affected product: Microsoft Windows 11. 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-2022-35838/ (Markdown: https://insights.sbomify.com/CVE-2022-35838/index.md)
```

## Sources

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

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