How severe is CVE-2019-14858?

CVE-2019-14858 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-14858?

CVE-2019-14858 affects the following packages: ansible (PyPI), ansible (PyPI), ansible (PyPI), ansible (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-14858?

Update ansible to 2.9.0rc4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14858 is resolved across your whole dependency graph.

How do I detect CVE-2019-14858 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-14858 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-14858 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-14858 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-14858?

CVE-2019-14858 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-14858?

CVE-2019-14858 is classified as CWE-117 (CWE-117), CWE-532 (CWE-532). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-14858 published, and has it been updated?

CVE-2019-14858 was published on October 14, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2019-14858 — ansible

MEDIUMFix: ansible/ansible#63405

CVE-2019-14858 is a medium-severity (CVSS 5.5) CWE-117 vulnerability in ansible. A fix is available for ansible — see the affected versions and patch details below.

Ansible leaks sensitive information to logs when told not to

Also known asGHSA-h653-95qw-h2mpPYSEC-2019-171

Published

Oct 14, 2019

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐍ansible🐍ansible🐍ansible🐍ansible

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ansible`	≥ 2.9.0a1&&< 2.9.0rc4	2.9.0rc4`pip install --upgrade 'ansible==2.9.0rc4'`
🐍PyPI	`ansible`	≥ 2.8.0a1&&< 2.8.6	2.8.6`pip install --upgrade 'ansible==2.8.6'`
🐍PyPI	`ansible`	≥ 2.7.0a1&&< 2.7.14	2.7.14`pip install --upgrade 'ansible==2.7.14'`
🐍PyPI	`ansible`	≥ 2.0&&< 2.6.20	2.6.20`pip install --upgrade 'ansible==2.6.20'`

Affected Products

2 products · 2 configurations

Application

ansible engineredhat

≥ 2.0 && ≤ 2.8.0

range

Application

ansible towerredhat

≥ 3.0 && ≤ 3.5.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ansible to 2.9.0rc4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14858 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Fixes for Red Hat OpenStack Platform (RHOSP) have been set to 'Moderate' because flaw exploitation requires running Ansible with increased verbosity which is not the RHOSP deployment default. Red Hat Gluster Storage no longer maintains its own version of Ansible. The fix will be provided from core Ansible.

Product	Fixed in	Advisory
Red Hat Ansible Engine 2.6 for RHEL 7	`ansible-0:2.6.20-1.el7ae`	RHSA-2019:3201
Red Hat Ansible Engine 2.7 for RHEL 7	`ansible-0:2.7.14-1.el7ae`	RHSA-2019:3202
Red Hat Ansible Engine 2.8 for RHEL 7	`ansible-0:2.8.6-1.el7ae`	RHSA-2019:3203
Red Hat Ansible Engine 2 for RHEL 7	`ansible-0:2.8.6-1.el7ae`	RHSA-2019:3207
Red Hat OpenStack Platform 13.0 (Queens)	`ansible-0:2.6.20-1.el7ae`	RHSA-2020:0756

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-14858 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works