Skip to main content
VulnerabilityPublished

CVE-2026-123036: ansible-core · CWE-209

Source GCVE Database

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

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

Data as of 5 Nov 2026, 13:17 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.23.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 5 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 5 Nov 2026.

What to do

Upgrade ansible-core to 2.23.0.

Affected software

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

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

AI-suggested

Users should avoid upgrading to or using ansible-core versions 2.19 and later until a fix is released. As a temporary mitigation, avoid passing sensitive data as extra variables or in variables files that could be exposed in error messages. Monitor vendor advisories for an official fix and apply it once available.

Description

Ansible-core versions starting from 2.19 introduced a regression where tasks marked with no_log: true still leak sensitive information in their exception messages. This occurs because the exception field is preserved and printed by default, exposing secret values in error outputs such as argument-validation errors, templating errors, and assertion failures. The issue does not exist in version 2.16, where error texts are properly censored.

References

Community reviews

Loading reviews…