CVE-2025-1634 is a high-severity (CVSS 7.5) CWE-401 vulnerability in io.quarkus:quarkus-resteasy. O3 Security confirms whether CVE-2025-1634 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Io.quarkus:quarkus-resteasy: memory leak in quarkus resteasy classic when client requests timeout
Real-World Exposure
io.quarkus:quarkus-resteasy☕io.quarkus:quarkus-resteasy☕io.quarkus:quarkus-resteasyReal-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 the quarkus-resteasy extension, which causes memory leaks when client requests with low timeouts are made. If a client request times out, a buffer is not released correctly, leading to increased memory usage and eventual application crash due to OutOfMemoryError.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-resteasy | ≥ 3.16.0.CR1&&< 3.19.1 | 3.19.1 |
| ☕Maven | io.quarkus:quarkus-resteasy | ≥ 3.9.0.CR1&&< 3.15.3.1 | 3.15.3.1 |
| ☕Maven | io.quarkus:quarkus-resteasy | all versions | 3.8.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-resteasy. 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:quarkus-resteasy to 3.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-1634 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-2025-1634 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-2025-1634. 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-2025-1634 in your dependencies?
O3 detects CVE-2025-1634 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.