Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115622· Medium 5.5

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

Data as of 18 Nov 2026, 23:07 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 18 Nov 2026.

What to do

Upgrade 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

If you cannot patch yet, users should avoid passing sensitive data to warn() or deprecate() calls or avoid relying solely on no_log: true to protect sensitive information in these contexts.

Description

CVE-2026-115622 is a vulnerability in ansible-core where sensitive values intended to be hidden by the no_log: true setting are instead exposed in cleartext within warning and deprecation messages. This occurs because these messages bypass the masking mechanism, causing secrets to be printed to stdout/stderr and potentially captured in logs or automation outputs.

References

Community reviews

Loading reviews…