Skip to content
VulniPulse
Medium5.9Red Hat Linux

Medium [CVE-2026-47863] Denial of Service in bufferTimeout operator

This medium-severity Red Hat Linux advisory covers CVE-2026-47863 affecting Exploit Intelligence, Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Debezium 3.

CVE-2026-47863 Published Aug 26, 2026Updated by vendor Aug 26, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

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 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In Reactor Core, applications that use the Flux.bufferTimeout operator with fairBackpressure enabled are vulnerable to a Denial of Service (DoS) condition.

Reactor Core 3.8.0 - 3.8.6 Reactor Core 3.7.19 and earlier This occurs when upstream components deliver items during an active flush, causing the processing pipeline to permanently hang and making the application unresponsive. This impact is considered Moderate because exploitation requires a specific, non-default application configuration or usage pattern.

Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-770.

Affected Red Hat products: Exploit Intelligence; Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Debezium 3; Red Hat build of Quarkus; Red Hat Data Grid 8; Red Hat Fuse 7. Will not fix / out of support: Exploit Intelligence; Red Hat Fuse 7.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions
  • 3.8.0
  • 3.8.6
  • 3.7.19

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, applications should avoid using the `Flux.bufferTimeout` operator with `fairBackpressure` enabled. Review application code for instances where `fairBackpressure` is explicitly enabled with `Flux.bufferTimeout` and consider alternative buffering strategies or disabling `fairBackpressure` if it is not strictly required for the application's functionality.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

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.