Upstream information
Description
A flaw was found in ansible-core. When a task marked `no_log: true` fails, the task result is censored before being emitted, but the `exception` field is retained because it is present in the PRESERVE allow-list in lib/ansible/_internal/_task.py, and the default stdout callback prints it through CallbackBase._handle_exception. As a result, sensitive values the operator explicitly asked to hide can be disclosed: module argument-validation errors echo the argument value, templating errors print an Origin source snippet (the failing line plus the two preceding lines of the variables file, exposing neighbouring secrets from an -e @secrets.yml file), and fail/assert messages are printed in full. Secret material supplied as extra variables or variables files can therefore leak to terminal output, CI logs, and the stdout logs of any automation wrapping ansible-playbook, even though every task touching the secrets is marked no_log: true. This is a regression introduced with the ansible-core 2.19 data-tagging/templating rework; the behaviour does not occur on 2.16, where the error text is correctly censored.SUSE information
Overall state of this security issue: Pending
This issue is currently rated as having moderate severity.
| CVSS detail | CNA (Red Hat) | SUSE |
|---|---|---|
| Base Score | 5.5 | 5.5 |
| Vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| Attack Vector | Local | Local |
| Attack Complexity | Low | Low |
| Privileges Required | Low | Low |
| User Interaction | None | None |
| Scope | Unchanged | Unchanged |
| Confidentiality Impact | High | High |
| Integrity Impact | None | None |
| Availability Impact | None | None |
| CVSSv3 Version | 3.1 | 3.1 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise Module for Package Hub 15 SP7 | ansible-core | Not affected |
| SUSE Linux Enterprise Module for Systems Management 15 SP7 | ansible-core | Not affected |
| SUSE Linux Enterprise Server 16.0 | ansible-core | Not affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | ansible-core | Not affected |
| openSUSE Leap 16.0 | ansible-core | Not affected |
| openSUSE Leap 16.1 | ansible-core | Affected |
| Products under Long Term Service Pack support and receiving important and critical security fixes. | ||
| SUSE Linux Enterprise Module for Systems Management 15 SP6 | ansible-core | Not affected |
| SUSE Linux Enterprise Server 15 SP4-LTSS | ansible-core | Not affected |
| SUSE Linux Enterprise Server 15 SP5-LTSS | ansible-core | Not affected |
| SUSE Linux Enterprise Server 15 SP6-LTSS | ansible-core | Not affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP4 | ansible-core | Not affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | ansible-core | Not affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | ansible-core | Not affected |
| Products past their end of life and not receiving proactive updates anymore. | ||
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | ansible-core | Not affected |
| openSUSE Leap 15.6 | ansible-core | Not affected |
SUSE Timeline for this CVE
CVE page created: Thu Nov 5 14:56:47 2026CVE page last modified: Fri Nov 6 17:00:22 2026