# CVE-2024-1726: Quarkus: security checks in resteasy reactive may trigger a denial of service

> Attackers can cause denial of service in Quarkus RESTEasy Reactive by triggering resource exhaustion on inherited endpoints due to delayed security checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2024
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-mv64-86g8-cqq7

## What is CVE-2024-1726?

CVE-2024-1726 is a medium-severity denial of service vulnerability in Red Hat build of Quarkus, published on 25 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2024-1726?

6 open source packages ship an affected version, including io.quarkus.resteasy.reactive:resteasy-reactive.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus.resteasy.reactive:resteasy-reactive` | Maven | All versions | 3.2.11.Final |
| `io.quarkus.resteasy.reactive:resteasy-reactive` | Maven | All versions | 3.2.11.Final |
| `io.quarkus.resteasy.reactive:resteasy-reactive` | Maven | From 3.3.0.CR1 | 3.7.4 |
| `io.quarkus.resteasy.reactive:resteasy-reactive` | Maven | From 3.3.0.CR1 | 3.7.4 |
| `io.quarkus.resteasy.reactive:resteasy-reactive` | Maven | From 3.8.0.CR1 | 3.8.0 |
| `io.quarkus.resteasy.reactive:resteasy-reactive` | Maven | From 3.8.0.CR1 | 3.8.0 |

## How do I fix CVE-2024-1726?

Upgrade io.quarkus.resteasy.reactive:resteasy-reactive to a fixed version for your release line: 3.2.11.Final, 3.7.4 or 3.8.0.

## Is CVE-2024-1726 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1726 and fix it if it is affected.

What it is: CVE-2024-1726 is a medium-severity denial of service vulnerability in Red Hat build of Quarkus, published on 25 Apr 2024. 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-2024-1726 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus.resteasy.reactive:resteasy-reactive (Maven): affected all versions; fixed in 3.2.11.Final
- io.quarkus.resteasy.reactive:resteasy-reactive (Maven): affected all versions; fixed in 3.2.11.Final
- io.quarkus.resteasy.reactive:resteasy-reactive (Maven): affected from 3.3.0.CR1; fixed in 3.7.4
- io.quarkus.resteasy.reactive:resteasy-reactive (Maven): affected from 3.3.0.CR1; fixed in 3.7.4
- io.quarkus.resteasy.reactive:resteasy-reactive (Maven): affected from 3.8.0.CR1; fixed in 3.8.0
- io.quarkus.resteasy.reactive:resteasy-reactive (Maven): affected from 3.8.0.CR1; fixed in 3.8.0

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

## Sources

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

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