GPU VulnDB

Database/Control plane, storage & DevOps

ansible-core: no_log secrets leak in cleartext through module warning and deprecation messages

CVSS 5.5CVE-2026-115622Control plane, storage & DevOpscurated

Impact

Tasks marked no_log: true still print sensitive values in cleartext when a module passes them to warn() or deprecate(). The result-censoring code keeps the 'warnings' and 'deprecations' keys on its allow-list, so those messages skip masking. On a fleet provisioned by Ansible, that means BMC passwords, registry tokens, cluster join tokens or cloud keys handled by such tasks can end up in terminal scrollback, CI job logs and any tooling that captures ansible-playbook output. Anyone who can read those logs gets the secrets, even though every task that touched them was marked no_log.

Who can reach it

Local or log-level access: anyone who can read the stdout/stderr of ansible-playbook runs, such as CI log viewers or users of a shared automation host. No exploit is needed beyond reading output a run has already produced. The leak only happens when a module actually emits a warning or deprecation containing the sensitive parameter.

What to do

Upgrade ansible-core once Red Hat or upstream ships the fix. The record does not name a fixed version. Until then, assume CI and automation logs from no_log tasks may contain secrets: restrict who can read them, purge retained logs where you can, and rotate any credential that may have been printed. It is a control-node package update with no node downtime.

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.