CVE
Red Hat Ansible Core secret leak via warning and deprecation messages
- Exploited
- No known exploitation
- Fix
- Fixed in 2.22.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.22.0.
Summary
A flaw in ansible-core, Red Hat's affected package, can leak sensitive values: when a task is marked no_log: true, secrets passed to warning and deprecation messages are printed in cleartext to stdout or stderr. An attacker with local access and low privileges can read those values from captured output such as terminal sessions or CI logs.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach16/20ansible-core: 4.3M downloads a week
- Severity5.5/10CVSS 5.5
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
Impact
- Widely used
ansible-core has 4.3m weekly downloads.Source: pypistats.org
150 packages depend on ansible-core.Source: deps.dev
What to do
Upgrade to a fixed version: 2.22.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-115622 (A flaw was found in ansible-core.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-115622 (entry last updated 2026-11-18):
Affected:
- PyPI package ansible-core: from 2.19.0, fixed in 2.22.0
Fixed versions: 2.22.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115622 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115622 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://access.redhat.com/security/cve/CVE-2026-115622
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-115622
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115622"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- ansible-corePyPI
From 2.19.0 · fixed in 2.22.0
Fixed in 2.22.0 (released Nov 2, 2026, 16 days before disclosure).
The latest release, 2.22.0, is not affected.
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-115622 |
| Record | NVD · CVE-2026-115622 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-115622 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115622
Is CVE-2026-115622 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-115622?
ansible-core (PyPI): from 2.19.0 before 2.22.0.Source: cve.now feed data
How do I fix CVE-2026-115622?
Upgrade to a fixed version: 2.22.0.Source: cve.now feed data