Skip to content

RHSA-2026:71113: Critical: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update

Reporting by Red Hat Security AdvisoriesRead the original at access.redhat.com

Objectivity score: 62 out of 100.
Difficulty 100 out of 100 (Quantum Electrodynamics)— Read Analysis

Executive Summary

The provided data lists several software packages and their corresponding SHA-256 hashes, primarily related to Automation Controller, EDA Controller, Gateway, Hub components, and associated Python libraries for various Red Hat Enterprise Linux (RHEL) distributions (EL9AP, EL10AP). The package list details components like the automation controller and its dependencies, as well as specific versions of Python packages such as `sqlparse` used in Ansible roles. There are separate entries for different target architectures (aarch64, x8664, s390x, ppc64le) across various components. The data suggests a compiled or distributed system environment involving controllers and underlying scripting/library dependencies configured across different operating systems and hardware types.

Facts Only

* automation-controller-4.7.17-1.el9ap.aarch64.rpm SHA-256: 50cf32f5a3f54f607764f07649f52a3948c2b32409caf4b00c290cc6eff05343
* automation-controller-cli-4.7.17-1.el9ap.noarch.rpm SHA-256: 971a6bef9d98827ffe8b536990ec2c1fcac5cefd0bb0f0c5fe54673d1a97a2c1
* automation-controller-server-4.7.17-1.el9ap.noarch.rpm SHA-256: 958bb43f8c8089c6a250c0749b676ada9a50c150689179bb55b57cfc6c6fb699
* automation-controller-ui-4.7.17-1.el9ap.noarch.rpm SHA-256: abadd1dcf701c517af49e02b4c380b5efa185d2fedc28c063f6cef8fe4ef5051
* automation-controller-venv-tower-4.7.17-1.el9ap.aarch64.rpm SHA-256: 66e8a2a6a048e9bc69ae79029b88b228de797613fee5018fb51d4738501df171
* automation-eda-controller-1.2.13-1.el9ap.noarch.rpm SHA-256: e5c81b81cf283ce4a454c3cfd820be11064060fc3a71c768cb59352b912675ef
* automation-eda-controller-base-1.2.13-1.el9ap.noarch.rpm SHA-256: a40ea90c667f2fd1b6397290e0fb836933694b9c32bc15a3a4cc1b6763d4f975
* automation-eda-controller-base-services-1.2.13-1.el9ap.noarch.rpm SHA-256: 9f8d1886f75b01e617c7f59c76dc2289c7c0d814366a9e495191dbbf07158fcf
* automation-eda-controller-event-stream-services-1.2.13-1.el9ap.noarch.rpm SHA-256: b83f270fa1f58e35b9d42bfe5521cc2c6c3c21172f0b49fb08be08498fe821c9
* automation-eda-controller-worker-services-1.2.13-1.el9ap.noarch.rpm SHA-256: 301e69517496c9aaaaaf541559f9044372182637ef8c3813417cda216e14dfe4
* automation-gateway-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 3aac2d1879e53cf432d2ca8ee6ed6cb7760b6fd472f2fe0be5bfcb200a456a1e
* automation-gateway-config-2.6.20260923-1.el9ap.noarch.rpm SHA-256: b4dd085fb97a5d3e681b49514673a0700d2ec859606d8b9bc7155086d46903cc
* automation-gateway-proxy-2.6.17-3.el9ap.aarch64.rpm SHA-256: 4c79ed6d9de1d4abd1aa74dbbd1941283b87a183f1182d71e790fddc9154973d
* automation-gateway-proxy-debugsource-2.6.17-3.el9ap.aarch64.rpm SHA-256: aec27dc6d4f19fb70c05cb29dcdb9e5f405beaabe6625ba0ba2613cd24a6065a
* automation-gateway-proxy-server-2.6.17-3.el9ap.aarch64.rpm SHA-256: 7bc5fb7a517e419dbb0c0afe33f4b9bf569658f3fc6d73a0a5ee917d3ab3b20f
* automation-gateway-proxy-server-debuginfo-2.6.17-3.el9ap.aarch64.rpm SHA-256: bb3d6da86727f4adfde1897675e20eb00a7ac77c22102140bdd75d96e32a5451
* automation-gateway-server-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 6b93768308dea4f69aac2f8e690c90e2d463114ec70fcca7da82ce975ccc976e
* automation-hub-4.11.14-1.el9ap.noarch.rpm SHA-256: 62ebbb0bd6db477ec828ebe038fbd1dae6ccf6ddb8a5e18945b32416be412d83
* automation-platform-ui-2.6.14-1.el9ap.noarch.rpm SHA-256: bfc7ca59cf64022bd4ea4c5df4395110c9cbecd32db0a4b84a46f82bbc2ffe59
* python3.12-django-ansible-base+activitystream-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 3ca5995a1054ce6095b03e9dbd17ce540b3c7948b439a0ba6a9b1cfbb18f4ebb
* python3.12-django-ansible-base+apidocumentation-2.6.20260923-1.el9ap.noarch.rpm SHA-256: d716040507aff5d8362dfafc1a2da79e8eb13dc4f82203992041b116a37637b7
* python3.12-django-ansible-base+authentication-2.6.20260923-1.el9ap.noarch.rpm SHA-256: da118dfb973e3253c6c5b53ff8f576558ad96fddc489bf1251db54bd7076a587
* python3.12-django-ansible-base+channelauth-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 1a5a1cd7aa1432f9cc3ee819b0c20de550b083b496e16349f842ca63895b649d
* python3.12-django-ansible-base+featureflags-2.6.20260923-1.el9ap.noarch.rpm SHA-256: e1717192431daa8708f90167a6ccf8e4fc2689995d4b979680316c613002e2cd
* python3.12-django-ansible-base+jwtconsumer-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 189a23646d8205df354bea998ca2dc4a725fed9f35beb069828934af035a8d9c
* python3.12-django-ansible-base+oauth2provider-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 2c0166e9b30868ae8978123b2f6487883a1fe386d5c5e736cbab5fcffe23e563
* python3.12-django-ansible-base+rbac-2.6.20260923-1.el9ap.noarch.rpm SHA-256: ecbf83b124d17197b03b9a3d1d19864b7280dfa6e3f783a5908089293862820f
* python3.12-django-ansible-base+redisclient-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 799abcd3681433837befaadfc0dd55bb8d4be10bb4bfb1fbcd5f74990e1381ac
* python3.12-django-ansible-base+resourceregistry-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 4f748c15cb954b07228eeaa3e9055e002ec6e8dc8e6799333940fd7b360827fd
* python3.12-django-ansible-base+restfilters-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 1e781d74d0961e7de2187a2f8a640217baf13ce421a4081bae261f5569c8dffd
* python3.12-django-ansible-base-2.6.20260923-1.el9ap.noarch.rpm SHA-256: 18df093f7d103fe3cec4c2441d8f5f803f1080c004d4fed9ab7180907e1712c3
* python3.12-galaxy-ng-4.11.14-1.el9ap.noarch.rpm SHA-256: 7e49b0ff17ae15199349b7772b73e566689f535c63a84fb9eeb4140cf8c49dbe
* python3.12-gitpython-3.1.60-1.el9ap.noarch.rpm SHA-256: f407fc8eaaff224116a1daec80abf8976690ef620ed03b923569af677d3fb78b
* python3.12-sqlparse-0.6.0-1.el9ap.noarch.rpm SHA-256: 0aa4de0fb60096fcdecddf0e8860dceafa5d477430d99ea1dfcef1114afc4f8c
* receptor-1.6.8-1.el9ap.aarch64.rpm SHA-256: 63e8c51036ef69bf01d028988d9e6e4ab8713bed63a92a491f2044e336128d8f
* receptor-debuginfo-1.6.8-1.el9ap.aarch64.rpm SHA-256: cb4a649a30b3b01f55be7f3fa1719e2fafbfc1a1af8f98857a992cd7f05c581c
* receptor-debugsource-1.6.8-1.el9ap.aarch64.rpm SHA-256: c478b5c7bfbe7d6e7946f35f2c75390739d90bf9e00846757bfffbe63a0bd353
* receptorctl-1.6.8-1.el9ap.noarch.rpm SHA-256: bf9aee0f2c4b17463809b666c15664be8d304aa642451f6cbe2705cf2bdbddfd
* receptorctl-1.6.8-1.el9ap.noarch.rpm SHA-256: bf9aee0f2c4b17463809b666c15664be8d304aa642451f6cbe2705cf2bdbddfd

Full Take

The structure of the provided data points toward a complex, distributed system infrastructure managed by Automation Controller and EDA Controller components, layered with Gateway services and a central Hub. The presence of specific Python packages tailored for Django/Ansible integration suggests a focus on automating the configuration and deployment processes across these systems. The architecture involves distinct functional layers: automation (controller), event data processing (eda-controller), external access/routing (gateway), and a central coordination point (hub).
The recurrence of dependencies, such as `python3.12-django-ansible-base` packages linked to specific feature flags (`authentication`, `rbac`, `oauth2provider`), implies a highly orchestrated operational model where functionality is segmented and controlled via configuration layers rather than monolithic deployment. The existence of separate builds for different architectures (aarch64, x8664) demonstrates a commitment to multi-platform delivery, which speaks to the scale or intended reach of this system.
The pattern suggests an intent to achieve fine-grained control over the entire operational stack through dependency management and conditional feature enablement. The central question is what specific state or boundary condition necessitates such granular separation across controllers and gateways; understanding the design philosophy behind partitioning the automation, data flow, and access layers will reveal the core assumptions about system resilience versus administrative complexity. If a failure occurs in one layer (e.g., an EDA controller), does the pattern inherently allow for graceful degradation based on the configuration flags present in another layer? What happens when feature flag synchronization across all components fails?

From the original · Red Hat Security Advisories

- Issued: - 2026-09-23 - Updated: - 2026-09-23 RHSA-2026:71113 - Security Advisory Synopsis Critical: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update Type/Severity Security Advisory: Critical Red Hat Lightspeed patch analysis Identify and remediate systems affected by this advisory.
Read the full story at access.redhat.com
RHSA-2026:71113: Critical: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update | Huntaegis