CVE-2024-1726 is a medium-severity (CVSS 5.3) CWE-281 vulnerability in io.quarkus.resteasy.reactive:resteasy-reactive. A fix is available for io.quarkus.resteasy.reactive:resteasy-reactive — see the affected versions and patch details below.
Quarkus: security checks for some inherited endpoints performed after serialization in resteasy reactive may trigger a denial of service
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2024-1726.
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.resteasy.reactive:resteasy-reactive☕io.quarkus.resteasy.reactive:resteasy-reactive☕io.quarkus.resteasy.reactive:resteasy-reactiveReal-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 discovered in the RESTEasy Reactive implementation in Quarkus. Due to security checks for some JAX-RS endpoints being performed after serialization, more processing resources are consumed while the HTTP request is checked. In certain configurations, if an attacker has knowledge of any POST, PUT, or PATCH request paths, they can potentially identify vulnerable endpoints and trigger excessive resource usage as the endpoints process the requests. This can result in a denial of service.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | ≥ 3.8.0.CR1&&< 3.8.0 | 3.8.0io.quarkus.resteasy.reactive:resteasy-reactive:3.8.0 |
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | ≥ 3.3.0.CR1&&< 3.7.4 | 3.7.4io.quarkus.resteasy.reactive:resteasy-reactive:3.7.4 |
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | all versions | 3.2.11.Finalio.quarkus.resteasy.reactive:resteasy-reactive:3.2.11.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus.resteasy.reactive:resteasy-reactive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus.resteasy.reactive:resteasy-reactive to 3.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-1726 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
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.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-1726 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Quarkus 3.2.11.Final | io.quarkus/quarkus-resteasy-reactive:3.2.11.Final-redhat-00001 | RHSA-2024:1662 |
Frequently Asked Questions
Is CVE-2024-1726 in your dependencies?
Find it across Maven, including transitive dependencies.