RHSA-2025:19734HighCVSS 7.5

Red Hat Security Advisory: pcs security update

Published
November 4, 2025
Last Modified
August 13, 2026

🔗 CVE IDs covered (5)

CVE-2025-61919 →CVE-2025-59830 →CVE-2025-61770 →CVE-2025-61771 →CVE-2025-61772 →

📋 Description

CVE-2025-59830 — rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters CVE-2025-61770 — rack: Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion) CVE-2025-61771 — rack: Rack's multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion) CVE-2025-61772 — rack: Rack memory exhaustion denial of service CVE-2025-61919 — rubygem-rack: Unbounded read in Rack::Request form parsing can lead to memory exhaustion

🎯 Affected products10

  • Red Hat Enterprise Linux High Availability E4S (v.8.6)
  • Red Hat Enterprise Linux High Availability TUS (v.8.6)
  • pcs-0:0.10.12-6.el8_6.10.ppc64le as a component of Red Hat Enterprise Linux High Availability E4S (v.8.6)
  • pcs-0:0.10.12-6.el8_6.10.src as a component of Red Hat Enterprise Linux High Availability E4S (v.8.6)
  • pcs-0:0.10.12-6.el8_6.10.src as a component of Red Hat Enterprise Linux High Availability TUS (v.8.6)
  • pcs-0:0.10.12-6.el8_6.10.x86_64 as a component of Red Hat Enterprise Linux High Availability E4S (v.8.6)
  • pcs-0:0.10.12-6.el8_6.10.x86_64 as a component of Red Hat Enterprise Linux High Availability TUS (v.8.6)
  • pcs-snmp-0:0.10.12-6.el8_6.10.ppc64le as a component of Red Hat Enterprise Linux High Availability E4S (v.8.6)
  • pcs-snmp-0:0.10.12-6.el8_6.10.x86_64 as a component of Red Hat Enterprise Linux High Availability E4S (v.8.6)
  • pcs-snmp-0:0.10.12-6.el8_6.10.x86_64 as a component of Red Hat Enterprise Linux High Availability TUS (v.8.6)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: No action is required for typical Rack applications that use the framework’s default request-handling mechanisms, as these are not impacted. For custom implementations or middleware that directly invoke Rack::QueryParser, administrators should: Use explicit delimiters: Configure QueryParser to use a specific delimiter (e.g. &) rather than accepting both & and ;. Limit request size and parameters: Enforce request size and parameter count limits at upstream layers (such as a web server, reverse proxy, or WAF) to prevent excessive resource consumption. Prefer safe APIs: Use Rack::Request or other higher-level request parsing APIs, which apply safe defaults and avoid this vulnerability. Workaround: 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. Workaround: No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability beyond these configuration-based workarounds.

🔗 References (8)