CVE-2024-1726
MEDIUMCVE-2024-1726 is a medium-severity (CVSS 5.3) CWE-281 vulnerability in io.quarkus.resteasy.reactive:resteasy-reactive. O3 Security confirms whether CVE-2024-1726 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Quarkus: security checks for some inherited endpoints performed after serialization in resteasy reactive may trigger a denial of service
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.0 |
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | ≥ 3.3.0.CR1&&< 3.7.4 | 3.7.4 |
| ☕Maven | io.quarkus.resteasy.reactive:resteasy-reactive | all versions | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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.
How O3 protects you
O3 pinpoints whether CVE-2024-1726 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-1726. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-1726 in your dependencies?
O3 detects CVE-2024-1726 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.