No-redaction of Sensitive Values in Ansible when no_log:true on Warning or Deprecation Calls
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | ansible-core | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Redhat | Ansible Core |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://access.redhat.com/security/cve/CVE-2026-115622 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat ansible Core |
|
| Vendors & Products |
Redhat
Redhat ansible Core |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | No-redaction of Sensitive Values in Ansible when no_log:true on Warning or Deprecation Calls |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in ansible-core. When a task or its parameters are marked no_log: 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 no_log: true. | |
| Weaknesses | CWE-532 | |
| References |
| |
| Metrics |
cvssV3_1
|