NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Quarkus does not terminate HTTP requests header contextGHSA-mwhw-6p27-4crc

CRITICAL

GHSA-mwhw-6p27-4crc is a critical-severity (CVSS 9.8) CWE-444 vulnerability in io.quarkus:quarkus-core-parent. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for io.quarkus:quarkus-core-parent — see the affected versions and patch details below.

Also known asCVE-2022-2466
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk
0.00%5.39%10.8%16.2%12.8%1.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕io.quarkus:quarkus-core-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavior. This issue was fixed in version 2.10.4Final.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.quarkus:quarkus-core-parent≥ 2.10.0&&< 2.10.42.10.4io.quarkus:quarkus-core-parent:2.10.4

Affected Products

1 product · 1 configurations
Application
quarkusquarkus
≥ 2.10.0 && < 2.10.4
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

It was found that Quarkus 2.10.x does not terminate HTTP requests header…

github.comNVDSep 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-core-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.quarkus:quarkus-core-parent to 2.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwhw-6p27-4crc is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavior. This issue was fixed in version 2.10.4Final.
O3 Security · Impact-Aware SCA

Is GHSA-mwhw-6p27-4crc in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Quarkus does not terminate HTTP requests header context