RHSA-2026:88200CriticalCVSS 9.0

Red Hat Security Advisory: Ansible automation portal Red Hat Enterprise Linux Images

Published
October 22, 2026
Last Modified
October 31, 2026

🔗 CVE IDs covered (6)

CVE-2026-100721 →CVE-2026-9496 →CVE-2026-19553 →CVE-2026-85393 →CVE-2026-87776 →CVE-2026-89011 →

📋 Description

CVE-2026-9496 — pacote: Pacote: Denial of Service via crafted spec.rawSpec value in addGitSha function CVE-2026-19553 — python: python: Certificate verification bypass via missing server_hostname validation in SSLContext.wrap_bio() CVE-2026-85393 — node-forge: node-forge: Signature forgery vulnerability in RSA PKCS#1 v1.5 verification CVE-2026-87776 — compression: compression: Denial of Service via memory leak on premature response close CVE-2026-89011 — isomorphic-git: isomorphic-git: Information disclosure via prototype pollution in getRemoteInfo function. CVE-2026-100721 — vm2: vm2 before 3.12.2 Authorization Bypass via Custom Resolver

🎯 Affected products2

  • Red Hat Ansible Automation Platform 2.2
  • registry.redhat.io/ansible-automation-platform/bootc-automation-portal-rhel9@sha256:7d6233bea4613d45dba38fdfba791bb3cb40aa77a8b2192a38d32e6e4b230529_amd64 as a component of Red Hat Ansible Automation Platform 2.2

✅ Remediation

For more about Ansible Portal Installer Bootc, see References links Workaround: To mitigate this limit the length of incoming package specifiers (spec.rawSpec) before they reach the resolution service. Enforce hard CPU time limits or timeouts on isolated build jobs and package resolution processes. Workaround: Restrict Python TLS clients to trusted networks so an on-path attacker cannot intercept sessions. Applications that use SSLContext.wrap_bio(), asyncio.create_connection(), or loop.start_tls() with check_hostname enabled must pass a non-empty server_hostname; hostname verification then proceeds and this flaw is not reachable. Optionally pin expected server certificates so a mismatched host certificate is rejected even if hostname checking is skipped. Workaround: Update the compression middleware to version 1.8.2 or later. No supported workaround is currently available if the affected version cannot be updated. 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.

🔗 References (10)