Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-16308] io.quarkus.resteasy.reactive/resteasy-reactive: Quarkus REST - Unbounded multipart MIME part-header accumulation allows remote OOM denial of service

This high-severity Red Hat Linux advisory covers CVE-2026-16308 affecting Cryostat 4 on RHEL 9, Red Hat build of Keycloak 26.4.14, Red Hat build of Keycloak 26.6.5.

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

CVE-2026-16308 Source published Source updated

VulniPulse record published Record updated

CVE-2026-16308
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Get an email when Red Hat Linux publishes the next one.

See Red Hat Linux's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts 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 Linux

Summary

IBM Enterprise Build of Quarkus 3.27.1 through 3.27.4.SP2, and 3.33.1 through 3.33.2.SP2 Quarkus REST could allow a remote attacker to cause a denial of service due to unbounded accumulation of multipart MIME part-header bytes.

An unauthenticated remote attacker can exploit this vulnerability by sending a crafted multipart/form-data request with an excessively large header section. This unbounded accumulation of MIME part-header bytes can exhaust the Java Virtual Machine (JVM) heap memory, leading to an OutOfMemoryError.

The primary consequence is a denial of service, causing the application to crash. This is an Important flaw in Quarkus REST / RESTEasy Reactive's MultipartParser, allowing an unauthenticated remote attacker to cause a denial of service.

This vulnerability does not require valid form field names or authentication. 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-770.

Affected Red Hat products: Cryostat 4 on RHEL 9; Red Hat build of Keycloak 26.4; Red Hat build of Keycloak 26.4.14; Red Hat build of Keycloak 26.6; Red Hat build of Keycloak 26.6.5; Red Hat build of Quarkus 3.27.4.SP3; Red Hat build of Quarkus 3.33.2.SP3; Streams for Apache Kafka 3.2.1; Cryostat 4; Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat OpenShift Dev Spaces; streams for Apache Kafka 2.

Affected versions
  • 3.27.1
  • 3.27.4.SP2
  • 3.33.1
  • 3.33.2.SP2

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

Fixed versions
  • cryostat/cryostat-reports-rhel9:4.2.0-14
  • cryostat/cryostat-rhel9:4.2.0-14
  • cryostat/jfr-datasource-rhel9:4.2.0-14
  • rhbk/keycloak-operator-bundle:26.4.14-1
  • rhbk/keycloak-rhel9:26.4-22
  • rhbk/keycloak-rhel9-operator:26.4-22
  • resteasy-reactive-common-processor
  • rhbk-openshift-rhel9/rhbk-openshift-rhel9
  • rhbk/keycloak-operator-bundle:26.6.5-1
  • rhbk/keycloak-rhel9:26.6-11
  • rhbk/keycloak-rhel9-operator:26.6-11
  • rhbk-keycloak-rhel9/rhbk-keycloak-rhel9
  • resteasy-reactive-client-processor
  • RHSA-2026:68333
  • RHSA-2026:50847
  • RHSA-2026:50846
  • RHSA-2026:50849
  • RHSA-2026:50848
  • RHSA-2026:47189
  • RHSA-2026:47172
  • RHSA-2026:54435

Official advisory · high-confidence parse· fetched 27 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 27 days ago·verify at source

All Red Hat Linux advisories

Android app · Google Play

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.