Information Exposure Through Log Files The advisory has been revoked - it doesn't affect any version of package ansible.src  (opens in a new tab)


Threat Intelligence

EPSS
2.77% (87th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-ANSIBLESRC-15324633
  • published21 Feb 2026
  • disclosed11 Jun 2018

Introduced: 11 Jun 2018

CVE-2018-10855  (opens in a new tab)
CWE-532  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ansible.src package and not the ansible.src package as distributed by RHEL.

Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible.