# CVE-2022-2466: Quarkus does not terminate HTTP requests header context

> Quarkus fails to terminate HTTP request header context, potentially causing unpredictable behavior in the application.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 31 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mwhw-6p27-4crc

## What is CVE-2022-2466?

CVE-2022-2466 is a critical vulnerability in quarkus, published on 31 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavior.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

2 open source packages ship an affected version, including io.quarkus:quarkus-core-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus:quarkus-core-parent` | Maven | From 2.10.0 | 2.10.4 |
| `io.quarkus:quarkus-core-parent` | Maven | From 2.10.0 | 2.10.4 |

Products: Quarkus Quarkus.

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

Upgrade io.quarkus:quarkus-core-parent to 2.10.4 or later.

## Is CVE-2022-2466 being exploited?

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

Public exploit code:

- https://github.com/yuxblank/CVE-2022-2466---Request-Context-not-terminated-with-GraphQL (github_poc): https://github.com/yuxblank/CVE-2022-2466---Request-Context-not-terminated-with-GraphQL

## Other vulnerabilities in quarkus

- [CVE-2022-4116](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8)
- [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1)
- [CVE-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8)
- [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8)
- [CVE-2023-6267](https://insights.sbomify.com/CVE-2023-6267/): Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations. (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2466 is a critical vulnerability in quarkus, published on 31 Aug 2022. 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-2022-2466 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-core-parent (Maven): affected from 2.10.0; fixed in 2.10.4
- io.quarkus:quarkus-core-parent (Maven): affected from 2.10.0; fixed in 2.10.4

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-2466/ (Markdown: https://insights.sbomify.com/CVE-2022-2466/index.md)
```

## Sources

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

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