Red Hat Security Advisory: General availability of the satellite/iop-host-inventory-rhel9 container image
🔗 CVE IDs covered (13)
📋 Description
CVE-2026-15911 — confluent-kafka: confluent-kafka: Information disclosure via improper TLS certificate validation in HashiCorp Vault integration CVE-2026-102925 — virtualenv: virtualenv: Arbitrary code execution via crafted paths in activation scripts CVE-2026-102930 — virtualenv: virtualenv: Arbitrary code execution via unverified downloaded seed wheels CVE-2026-102937 — virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in Windows activation script CVE-2026-102938 — virtualenv: virtualenv: Arbitrary code execution via configuration injection in prompt values CVE-2026-113718 — virtualenv: virtualenv: arbitrary code execution via improper quoting in xonsh activation scripts CVE-2026-113722 — virtualenv: virtualenv: arbitrary code execution via improperly quoted interpreter paths in script launchers CVE-2026-113723 — virtualenv: virtualenv: Arbitrary code execution via malicious prompt text CVE-2026-113725 — virtualenv: virtualenv: arbitrary code execution via crafted environment name CVE-2026-113726 — virtualenv: virtualenv: Arbitrary command execution via unescaped prompt variables in zsh CVE-2026-113732 — virtualenv: virtualenv: Arbitrary code execution via improperly quoted Fish activation scripts CVE-2026-113776 — virtualenv: virtualenv: Arbitrary command execution via sequential placeholder substitution in activation templates CVE-2026-115586 — virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in bash activation script
🎯 Affected products2
- Red Hat Satellite 6.19
- registry.redhat.io/satellite/iop-host-inventory-rhel9@sha256:be649ce0d8fcb6169cca9fa76e473f30edf90d8a916e46a97db012914d897e45_amd64 as a component of Red Hat Satellite 6.19
✅ Remediation
For Red Hat Lightspeed in Satellite installation see the Red Hat Satellite documentation. 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. There is no configuration workaround in affected versions because TLS certificate verification is hardcoded to disabled. The upstream confluent-kafka Python package addressed this issue in version 2.15.0, which enables TLS certificate verification by default and allows supplying a CA bundle through the ssl.ca.location configuration option or the VAULT_CACERT environment variable for Vault servers that present certificates signed by a private or internal certificate authority. Updating to a version of the confluent-kafka Python package that enables TLS certificate verification, or updating affected Red Hat products once they incorporate the fixed version, is the recommended resolution. Workaround: Avoid creating, copying, or distributing virtual environments whose path contains characters such as ', `, $, ;, (, or ), and inspect the generated activation script before sourcing one that you did not create; these precautions prevent shell metacharacters embedded in a crafted path from being executed when an activation script is sourced. The upstream project has released a fixed version of virtualenv, so updating to a version that includes the fix (21.7.13 or later, or a product update containing it) also addresses the issue. 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: Strip line boundaries (such as newline, carriage return, and other Unicode line-separator characters) from any value before using it as --prompt or VIRTUALENV_PROMPT, and do not pass externally influenced data -- for example user-supplied strings or CI-derived values such as branch names -- as the virtualenv prompt. Ensure the VIRTUALENV_PROMPT environment variable and any configuration file that sets the prompt are sourced only from trusted input. The upstream project fixed this issue in virtualenv 21.7.11 by collapsing line boundaries when writing pyvenv.cfg, so updating to a version that contains this fix resolves the issue. For Red Hat products that bundle virtualenv, apply updates through the respective product channels. Workaround: --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to ensure virtualenv serializes prompt and path values in xonsh activation scripts as pure ASCII escape sequences rather than raw multibyte characters: upgrade to virtualenv 21.14.9 (or the fixed Uv/Rhoai/Odh Kserve Agent Rhel/Rhoai/Odh Kserve Controller Rhel/Rhoai/Odh Kserve Router Rhel/Rhoai/Odh Kserve Storage Initializer Rhel/Python Virtualenv/Rhoai/Odh Feature Server Rhel/Python3.11 Virtualenv/Python3.12 Virtualenv/Devspaces/Udi Rhel/Rhoai/Odh Ta Lmes Job Rhel/Cloudservices/Advisor Backend/Satellite/Iop Host Inventory Rhel/Satellite/Iop Yuptoo Rhel/Ansible Automation Platform 26/Lightspeed Chatbot Rhel/Satellite/Iop Advisor Backend Rhel/Ansible Automation Platform 26/Controller Rhel/Ansible Automation Platform 27/Controller Rhel/Ansible Ai Connect Service/Insights Host Inventory/Rhoai/Odh Training Rocm64 Torch28 Py312 Rhel/Cloudservices/Ros Backend/Redhat User Workloads/Mintmaker Renovate Image/Koku Daily/Nise Populator/Openshift Lightspeed/Lightspeed Service Api Rhel/Rhoai/Odh Trustyai Nemo Guardrails Server Rhel/Ansible Chatbot Stack/Rhoai/Odh Workbench Codeserver Datascience Cpu Py312 Rhel/Rhoai/Odh Workbench Jupyter Datascience Cpu Py312 Rhel/Rhoai/Odh Workbench Jupyter Pytorch Llmcompressor Cuda Py312 Rhel/Cloudservices/Rbac/Cloudservices/Yuptoo/Rhel Cla/Rlsapi Rhel/Rhai Early Access/Docling Serve Cuda Rhel/Digital Roadmap Backend/Ansible Automation Platform 27/Eda Controller Rhel/Automation Hub Container/Ansible Automation Platform 26/Eda Controller Rhel/Vulnerability Engine builds), which replace repr() with ascii() in XonshActivator.quote to serialize all non-ASCII characters as ASCII escape sequences, closing all 2 injection vectors (crafted prompt arguments, crafted destination directory paths). Until patched, this is a concern on Environments where virtualenv-generated xonsh activation scripts are sourced in shell sessions using legacy multibyte encodings, so Audit and restrict virtualenv prompt arguments and destination directory paths to trusted inputs, and enforce UTF-8 source decoding across xonsh sessions. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper quoting defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high) Workaround: --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to eliminate unquoted shell wrapper invocations by enforcing safe argument quoting or direct process execution for POSIX script launchers: upgrade to virtualenv 21.14.9 (or the fixed Uv/Rhoai/Odh Kserve Agent Rhel/Rhoai/Odh Kserve Controller Rhel/Rhoai/Odh Kserve Router Rhel/Rhoai/Odh Kserve Storage Initializer Rhel/Python Virtualenv/Rhoai/Odh Feature Server Rhel/Python3.11 Virtualenv/Python3.12 Virtualenv/Devspaces/Udi Rhel/Rhoai/Odh Ta Lmes Job Rhel/Cloudservices/Advisor Backend/Satellite/Iop Host Inventory Rhel/Satellite/Iop Yuptoo Rhel/Ansible Automation Platform 26/Lightspeed Chatbot Rhel/Satellite/Iop Advisor Backend Rhel/Ansible Automation Platform 26/Controller Rhel/Ansible Automation Platform 27/Controller Rhel/Ansible Ai Connect Service/Insights Host Inventory/Rhoai/Odh Training Rocm64 Torch28 Py312 Rhel/Cloudservices/Ros Backend/Redhat User Workloads/Mintmaker Renovate Image/Koku Daily/Nise Populator/Openshift Lightspeed/Lightspeed Service Api Rhel/Rhoai/Odh Trustyai Nemo Guardrails Server Rhel/Ansible Chatbot Stack/Rhoai/Odh Workbench Codeserver Datascience Cpu Py312 Rhel/Rhoai/Odh Workbench Jupyter Datascience Cpu Py312 Rhel/Rhoai/Odh Workbench Jupyter Pytorch Llmcompressor Cuda Py312 Rhel/Cloudservices/Rbac/Cloudservices/Yuptoo/Rhel Cla/Rlsapi Rhel/Rhai Early Access/Docling Serve Cuda Rhel/Digital Roadmap Backend/Ansible Automation Platform 27/Eda Controller Rhel/Automation Hub Container/Ansible Automation Platform 26/Eda Controller Rhel/Vulnerability Engine builds), which quote interpreter executable paths using shlex.quote with backslash escaping in shell shebangs and rewrite pip-generated launchers during environment seeding, closing all 2 injection vectors (crafted environment destination path with shell command substitutions, long destination directory path exceeding shebang length limits). Until patched, this is only a concern on Linux systems where virtualenv creates POSIX console script launchers in attacker-influenced directory paths — non-POSIX platforms including Windows are unaffected — so restrict and audit who can specify virtual environment destination paths, ensure paths do not contain shell metacharacters or exceed 127 bytes, and regenerate existing launchers. As …
🔗 References (20)
- selfhttps://access.redhat.com/errata/RHSA-2026:95662
- externalhttps://access.redhat.com/documentation/en-us/red_hat_satellite/6.19/html/updating_red_hat_satellite/index
- externalhttps://access.redhat.com/security/cve/CVE-2026-102925
- externalhttps://access.redhat.com/security/cve/CVE-2026-102930
- externalhttps://access.redhat.com/security/cve/CVE-2026-102937
- externalhttps://access.redhat.com/security/cve/CVE-2026-102938
- externalhttps://access.redhat.com/security/cve/CVE-2026-113718
- externalhttps://access.redhat.com/security/cve/CVE-2026-113722
- externalhttps://access.redhat.com/security/cve/CVE-2026-113723
- externalhttps://access.redhat.com/security/cve/CVE-2026-113725
- externalhttps://access.redhat.com/security/cve/CVE-2026-113726
- externalhttps://access.redhat.com/security/cve/CVE-2026-113732
- externalhttps://access.redhat.com/security/cve/CVE-2026-113776
- externalhttps://access.redhat.com/security/cve/CVE-2026-115586
- externalhttps://access.redhat.com/security/cve/CVE-2026-15911
- externalhttps://access.redhat.com/security/updates/classification/
- externalhttps://catalog.redhat.com/software/containers/search
- externalhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.19/html/installing_satellite_server_in_a_connected_network_environment/performing-additional-configuration-on-server_satellite#installing-and-configuring-red-hat-lightspeed-in-satellite
- externalhttps://docs.redhat.com/en/documentation/red_hat_satellite/6.19/html/installing_satellite_server_in_a_disconnected_network_environment/performing-additional-configuration#installing-and-configuring-red-hat-lightspeed-in-satellite
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_95662.json