Skip to main content
VulnerabilityPublished

CVE-2026-123036: Red Hat ansible-core · Generation of Error Message Containing Sensitive Information

Affects Red Hat ansible-coreSource CVE Database V5

0
Compare

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

Data as of 5 Nov 2026, 10:05 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 Red Hat 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

Upgrade ansible-core to version 2.23.0 or later where this issue is fixed. Until then, be aware that marking tasks with no_log: true does not fully prevent sensitive data leakage in error messages. No other vendor advisory mitigation or workaround is provided.

Description

CVE-2026-123036 is a vulnerability in Red Hat ansible-core versions 2.19.0 through 2.22.x where sensitive information can be leaked despite tasks being marked with no_log: true. This occurs because the exception field is preserved and printed in error messages, exposing secret variables in terminal output and logs. The issue was introduced in version 2.19 and fixed in 2.23.0.

References

Community reviews

Loading reviews…