Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2025-1634] Io.quarkus:quarkus-resteasy: memory leak in quarkus resteasy classic when client requests timeout

This high-severity Red Hat Linux advisory covers CVE-2025-1634 affecting Red Hat Build of Apache Camel 4.8 for Quarkus 3.15, Red Hat build of Quarkus 3.15.3.SP1, Red Hat build of Quarkus 3.8.6.SP3.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2025-1634 Source published Source updated

VulniPulse record published

CVE-2025-1634
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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.

This vulnerability is marked as and Important severity rather than Moderate because it allows an unauthenticated attacker to trigger a denial of service condition by repeatedly sending crafted HTTP requests with low timeouts.

The issue leads to a memory leak that cannot be recovered without restarting the application, ultimately resulting in an OutOfMemoryError and complete service failure. In a production environment, this vulnerability poses a significant risk to availability, especially for applications handling multiple concurrent requests.

Since no mitigation exists, all applications using quarkus-resteasy are affected until patched. The ease of exploitation, lack of required privileges, and high impact on service uptime justify the high severity rating.

Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-401.

Affected products named by the advisory: Red Hat Build of Apache Camel 4.8 for Quarkus 3.15; Red Hat build of Quarkus 3.15.3.SP1; Red Hat build of Quarkus 3.8.6.SP3; Streams for Apache Kafka 2.9.1; and 2 more.

Is CVE-2025-1634 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2025-1634 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2025-1634?

Upgrade to a fixed release named by Red Hat:

  • quarkus-resteasy
  • RHSA-2025:2067
  • RHSA-2025:1885
  • RHSA-2025:1884
  • RHSA-2025:9922
  • RHSA-2025:12511
  • RHSA-2025:23417

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Fixed versions
  • quarkus-resteasy
  • RHSA-2025:2067
  • RHSA-2025:1885
  • RHSA-2025:1884
  • RHSA-2025:9922
  • RHSA-2025:12511
  • RHSA-2025:23417

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 20 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.