RHSA-2025:19832HighCVSS 8.0

Red Hat Security Advisory: Satellite 6.17.6 Async Update

Published
November 5, 2025
Last Modified
August 13, 2026

🔗 CVE IDs covered (3)

CVE-2025-10622 →CVE-2025-59830 →CVE-2025-61919 →

📋 Description

CVE-2025-10622 — foreman: OS command injection via ct_location and fcct_location parameters CVE-2025-59830 — rubygem-rack: Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters CVE-2025-61919 — rubygem-rack: Unbounded read in Rack::Request form parsing can lead to memory exhaustion

🎯 Affected products37

  • Red Hat Satellite 6.17 for RHEL 9
  • candlepin-0:4.4.23-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • candlepin-0:4.4.23-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • candlepin-selinux-0:4.4.23-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-0:3.14.0.10-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-bootloaders-redhat-0:202506020000-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-bootloaders-redhat-0:202506020000-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-bootloaders-redhat-tftpboot-0:202506020000-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-cli-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-debug-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-dynflow-sidekiq-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-ec2-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-journald-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-libvirt-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-openstack-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-ovirt-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-pcp-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-postgresql-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-redis-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-service-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-telemetry-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • foreman-vmware-0:3.14.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-foreman_maintain-1:1.10.4-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-foreman_maintain-1:1.10.4-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-katello-0:4.16.0.10-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-katello-0:4.16.0.10-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-rack-0:2.2.20-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-rack-0:2.2.20-1.el9sat.src as a component of Red Hat Satellite 6.17 for RHEL 9
  • rubygem-smart_proxy_openscap-0:0.12.1-1.el9sat.noarch as a component of Red Hat Satellite 6.17 for RHEL 9
  • +7 more not shown

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html/updating_red_hat_satellite/index 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 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: 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 (14)