cve.bz

CVE-2026-115622 red hat ansible-core

5.5 mediumEPSS 0.1%

Medium (5.5) in red hat ansible-core. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-115622 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115622?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115622?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115622 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Red Hat ansible-corefrom 2.19.0 before 2.22.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14ansible-coreno fix listedDEBIAN-CVE-2026-115622
Ubuntu22.04:LTSansible-coreno fix listedUBUNTU-CVE-2026-115622
Ubuntu24.04:LTS, 26.04:LTS, 26.10ansible, ansible-coreno fix listedUBUNTU-CVE-2026-115622
UbuntuPro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 2 moreansibleno fix listedUBUNTU-CVE-2026-115622

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON