Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2019-14858 ansible

MEDIUM

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
Aug 7, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Sep 17, 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 CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2019-14858 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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
EcosystemPackageVulnerable rangeFix
🐍PyPIansible2.9.0a1&&< 2.9.0rc42.9.0rc4pip install --upgrade 'ansible==2.9.0rc4'
🐍PyPIansible2.8.0a1&&< 2.8.62.8.6pip install --upgrade 'ansible==2.8.6'
🐍PyPIansible2.7.0a1&&< 2.7.142.7.14pip install --upgrade 'ansible==2.7.14'
🐍PyPIansible2.0&&< 2.6.202.6.20pip install --upgrade 'ansible==2.6.20'

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-14858 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2019-14858. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

ProductFixed inAdvisory
Red Hat Ansible Engine 2.6 for RHEL 7ansible-0:2.6.20-1.el7aeRHSA-2019:3201
Red Hat Ansible Engine 2.7 for RHEL 7ansible-0:2.7.14-1.el7aeRHSA-2019:3202
Red Hat Ansible Engine 2.8 for RHEL 7ansible-0:2.8.6-1.el7aeRHSA-2019:3203
Red Hat Ansible Engine 2 for RHEL 7ansible-0:2.8.6-1.el7aeRHSA-2019:3207
Red Hat OpenStack Platform 13.0 (Queens)ansible-0:2.6.20-1.el7aeRHSA-2020:0756

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2019-14858 in your dependencies?

O3 Security finds CVE-2019-14858 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2019-14858: ansible (Medium 5.5) | O3 Security