io.quarkus.http/quarkus-http-core: Quarkus HTTP Cookie SmugglingGHSA-cxrx-q234-m22m
HIGHFix: quarkusio/quarkus-http#170GHSA-cxrx-q234-m22m is a high-severity (CVSS 7.4) CWE-444 vulnerability in io.quarkus.http:quarkus-http-core. A fix is available for io.quarkus.http:quarkus-http-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-cxrx-q234-m22m.
EPSS Exploitation Probability
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
io.quarkus.http:quarkus-http-coreReal-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
A flaw was found in Quarkus-HTTP, which incorrectly parses cookies with certain value-delimiting characters in incoming requests. This issue could allow an attacker to construct a cookie value to exfiltrate HttpOnly cookie values or spoof arbitrary additional cookie values, leading to unauthorized data access or modification. The main threat from this flaw impacts data confidentiality and integrity.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus.http:quarkus-http-core | all versions | 5.3.4io.quarkus.http:quarkus-http-core:5.3.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus.http:quarkus-http-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus.http:quarkus-http-core to 5.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxrx-q234-m22m is resolved across your whole dependency graph.
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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat has evaluated this vulnerability. This is a very similar vulnerability to an Undertow, seen in CVE-2023-4639.
| Product | Fixed in | Advisory |
|---|---|---|
| Cryostat 4 on RHEL 9 | cryostat/cryostat-agent-init-rhel9:0.5.0-6 | RHSA-2025:3018 |
| HawtIO HawtIO 4.2.0 | quarkus-http-core | RHSA-2025:8761 |
| Red Hat Build of Keycloak | see advisory | RHBA-2025:7525 |
| Red Hat build of Keycloak 26.2 | rhbk/keycloak-operator-bundle:26.2.4-2 | RHBA-2025:7639 |
| Red Hat build of Quarkus 3.15.3 | quarkus-http-core | RHSA-2025:0900 |
Frequently Asked Questions
Is GHSA-cxrx-q234-m22m in your dependencies?
Find it across Maven, including transitive dependencies.