Skip to content
statance
MenuClose
Log inStart for free ↗
medium · CVSS 4.1

CVE-2026-71462

Automation-controller: automation-controller-container: automation-controller: custom_venv_path setting provides filesystem path-existence oracle on control pod

Published 23 Sept 2026 · Source updated 5 Nov 2026 · Retrieved 2026-11-05 22:56 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

StringListPathField.to_internal_value() calls os.path.exists() on unbounded user-supplied paths. 200 vs 400 response reveals existence of arbitrary absolute paths on the controller-web pod. Tenant superuser can confirm /etc/tower/SECRET_KEY, k8s service-account token, receptor sockets, ConfigMap mount points. Mainly impactful on managed AAP (ansiblecloud.com) where tenant admin != host admin.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
automation-controllerRed Hatunaffected: 0:4.6.33-1.el8ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.6.33-1.el8ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.6.33-1.el9ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.6.33-1.el9ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.7.17-1.el9ap to < *See vendor advisory
automation-controllerRed Hatunaffected: 0:4.7.17-1.el9ap to < *See vendor advisory
ansible-automation-platform-26/controller-rhel9Red Hatunaffected: 1789673739 to < *See vendor advisory
ansible-automation-platform-27/controller-rhel9Red Hatunaffected: 1789580684 to < *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed