Bug 2559427 (CVE-2026-115622) - CVE-2026-115622 ansible-core: sensitive parameter leakage via warning and deprecation messages despite no_log: true
Summary: CVE-2026-115622 ansible-core: sensitive parameter leakage via warning and dep...
Keywords:
Status: NEW
Alias: CVE-2026-115622
Product: Security Response
Classification: Other
Component: vulnerability-draft
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-23 01:28 UTC by OSIDB Bzimport
Modified: 2026-11-12 15:49 UTC (History)
82 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-23 01:28:20 UTC
A flaw was found in ansible-core. When executing modules where tasks or parameters are marked with `no_log: true`, sensitive parameters passed to `module.warn()` or `module.deprecate()` are preserved and printed directly to stdout/stderr in warning and deprecation messages. In `lib/ansible/_internal/_task.py`, the censorship mechanism (`censor_callback_result=True`) explicitly preserves keys such as 'warnings' and 'deprecations' in `PRESERVE`, allowing sensitive data to bypass masking and be logged in plain text.


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