CVE-2026-115622: Medium severity pypi/ansible-core vulnerability
A flaw was found in ansible-core. When a task or its parameters are marked nolog: true, sensitive values passed to a module's warn() or deprecate() calls are not redacted and are printed in cleartext to stdout/stderr in warning and deprecation messages. The 'warnings' and 'deprecations' keys are retained in the PRESERVE allow-list in lib/ansible/internal/task.py when the task result is censored, so sensitive parameters bypass masking and can be disclosed in output captured in terminal sessions, CI logs, and any automation wrapping ansible-playbook, even though every task touching the secrets is marked nolog: true.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this disclosure?
Users of ansible-core are exposed when a task with no_log: true passes sensitive values to a module that emits them through warn() or deprecate(). The values can be captured in terminal output, CI logs, and output collected by automation around ansible-playbook.
Does marking every secret-handling task with no_log: true prevent this exposure?
No. Warning and deprecation messages are retained when the task result is censored, allowing sensitive parameters included in those messages to bypass masking.
What must an attacker or observer have to obtain the sensitive values?
They need access to output produced by the affected playbook run, such as an interactive terminal session, CI logs, or logs captured by automation invoking ansible-playbook. Exploitation does not require user interaction.