Bug 2567188 (CVE-2026-123036) - CVE-2026-123036 ansible-core: no_log does not censor the task exception field, leaking secret values via the default stdout callback
Summary: CVE-2026-123036 ansible-core: no_log does not censor the task exception field...
Keywords:
Status: NEW
Alias: CVE-2026-123036
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-05 07:23 UTC by OSIDB Bzimport
Modified: 2026-11-06 07:44 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-05 07:23:44 UTC
Verbatim report from Maksym Mazura via secalert. Impacted project ansible-core, verified on 2.21.5; `exception` listed in PRESERVE in lib/ansible/_internal/_task.py on v2.21.6rc1, v2.22.0rc2 and devel; not reproducible on 2.16.3. Three leak vectors: (1) module arg-validation value echoed, (2) templating Origin snippet of the vars file (failing line + two preceding lines), (3) full fail/assert msg; also under -vvv. INLINE reproducer provided: sec.yml (secret_a !unsafe "FAKEUNSAFE111", secret_b "FAKEPLAIN222 {{ nosuchvar }}"); pb.yml (command echo {{secret_b}}, wait_for port {{secret_a}}, fail msg {{secret_a}} - all no_log:true ignore_errors:true); run: ansible-playbook -i localhost, -c local -e @sec.yml pb.yml. Output on 2.21.5 shows FAKEUNSAFE111 and the secret_b line (plus preceding secret_a line) next to the "censored" notice. Suggested fix: do not preserve `exception` (or replace its message) when the result is censored, as 2.16 did; or have CallbackBase._handle_exception print fixed text for censored results. NOTE: no reproducer file/attachment was attached to the ticket - only the inline steps above; Red Hat has not yet independently reproduced. Disclosure: not public, no bounty requested.


Note You need to log in before you can comment on or make changes to this bug.