Skip to main content
VulnerabilityPublished

CVE-2026-115622: Red Hat ansible-core · Sensitive Data in Logs

Affects Red Hat ansible-coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.22.0 when convenient.

Data as of 18 Nov 2026, 19:49 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.15.5
Patch
Available – fixed in 2.22.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Red Hat ansible-core to 2.22.0.

Affected software

ProductAffectedFixed in
Red Hatansible-coreAffected
  • >=2.19.0 <2.22.0
Fixed in
  • 2.22.0
PyPIansible-corepkg:pypi/ansible-coreOther threatsAffected
  • >=2.19.0 <2.22.0
Fixed in
  • 2.22.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade ansible-core to version 2.22.0 or later where this issue is fixed. Until upgrading, avoid using warn() or deprecate() calls with sensitive parameters in tasks marked no_log: true, or ensure outputs are not captured or exposed in logs or terminals. The vendor advisory from Red Hat should be consulted for detailed remediation guidance.

Description

CVE-2026-115622 is a vulnerability in Red Hat ansible-core versions 2.19.0 through 2.21.x where sensitive information marked with no_log: true is not properly redacted in warning and deprecation messages. This causes sensitive data to be exposed in cleartext in stdout/stderr outputs, including terminal sessions, CI logs, and automation wrappers, despite tasks being marked to suppress logging. The issue is fixed in version 2.22.0.

References

Community reviews

Loading reviews…