GPU VulnDB

Database/Control plane, storage & DevOps

Ansible automation-controller: provisioning-callback secret leaks to read-only users and X-Forwarded-For is trusted

CVSS 9.9CVE-2026-84474Control plane, storage & DevOpscurated

Impact

automation-controller exposes a job template's host_config_key provisioning secret to anyone holding only view_jobtemplate, both in the API representation and in the activity stream. The provisioning callback endpoint then decides which host is calling from a client-supplied X-Forwarded-For header, which is attacker-controlled when the controller sits behind the AAP gateway with an empty proxy allow-list. A minimally privileged (or, in that gateway configuration, unauthenticated) remote attacker can therefore launch an existing job template against any host in its inventory using the template's own credentials. On a fleet where AAP drives node provisioning, firmware rollout or GPU driver installs, that is remote code execution on managed GPU nodes with whatever privilege the automation credential carries, scored 9.9 with a changed scope.

Who can reach it

Network access to the automation-controller API with a low-privileged account that can view a job template; unauthenticated when the controller is behind the AAP gateway with an empty proxy allow-list.

What to do

Apply the Red Hat errata for your AAP release (RHSA-2026:71113/71114/71115/71177/71179 cover 2.4 through 2.7) and restart the automation-controller services; no node reboot is required. Until patched, rotate host_config_key on every job template, disable provisioning callbacks where they are not needed, and populate the gateway proxy allow-list so X-Forwarded-For is not taken from clients.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.