CVE-2019-14858· NVD / CVE Program· CNA redhat

A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5.

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: ansible (Alpine:v3.10) 2.8.6-r0; ansible-base (Alpine:v3.13) 2.8.6-r0; ansible (Alpine:v3.8) 2.6.20-r0.

Low priority for now. Upgrade to ansible (Alpine:v3.10) 2.8.6-r0; ansible-base (Alpine:v3.13) 2.8.6-r0; ansible (Alpine:v3.8) 2.6.20-r0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Published: Oct 14, 2019
Updated: Jun 16, 2026
EPSS: 0.4% · 35th percentile
CWE: CWE-117

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CNA vs NVD score

NVD: 5.5
CNA · redhat: 7.3; 1.8 point gap

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
redhat	ansible engine	cpe:2.3:a:redhat:ansible_engine
redhat	ansible tower	cpe:2.3:a:redhat:ansible_tower

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

redhat ansible engine2.0 and later · up to 2.8.0 inclusive
redhat ansible tower3.0 and later · up to 3.5.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

Red Hat Ansible
- ansible_engine-2.x up to 2.8, ansible_tower-3.x up to 3.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.10	ansible	before 2.8.6-r0	2.8.6-r0
Alpine:v3.13	ansible-base	before 2.8.6-r0	2.8.6-r0
Alpine:v3.8	ansible	before 2.6.20-r0	2.6.20-r0
Alpine:v3.9	ansible	before 2.7.14-r0	2.7.14-r0
Debian:12	ansible	before 2.8.6+dfsg-1	2.8.6+dfsg-1
openSUSE:Leap 15.1	ansible	before 2.9.6-lp151.2.7.1	2.9.6-lp151.2.7.1
openSUSE:Tumbleweed	ansible-10	before 10.6.0-1.1	10.6.0-1.1
openSUSE:Tumbleweed	ansible-11	before 11.11.0-1.1	11.11.0-1.1
openSUSE:Tumbleweed	ansible-12	before 12.2.0-1.1	12.2.0-1.1
openSUSE:Tumbleweed	ansible-13	before 13.7.0-1.1	13.7.0-1.1
openSUSE:Tumbleweed	ansible-9	before 9.8.0-1.1	9.8.0-1.1
PyPI	ansible	from 2.0 · before 2.8.1	2.8.1
PyPI	ansible	from 2.0 · before 2.6.20	2.6.20
PyPI	ansible	from 2.7.0a1 · before 2.7.14	2.7.14
PyPI	ansible	from 2.8.0a1 · before 2.8.6	2.8.6
PyPI	ansible	from 2.9.0a1 · before 2.9.0rc4	2.9.0rc4
Red Hat:ansible_engine:2.6::el7	ansible	before 0:2.6.20-1.el7ae	0:2.6.20-1.el7ae
Red Hat:ansible_engine:2.7::el7	ansible	before 0:2.7.14-1.el7ae	0:2.7.14-1.el7ae
Red Hat:ansible_engine:2.8::el7	ansible	before 0:2.8.6-1.el7ae	0:2.8.6-1.el7ae
Red Hat:ansible_engine:2.8::el8	ansible	before 0:2.8.6-1.el8ae	0:2.8.6-1.el8ae
SUSE:Package Hub 15 SP1	ansible	before 2.9.6-bp151.3.6.1	2.9.6-bp151.3.6.1

Same product

redhat: all records

Other highest-scoring records for the same primary product.

CVE-2021-20228A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protected by the no_log feature when
31Monitor
CVE-2020-1737A flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip mo
31Monitor
CVE-2019-14846In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG
31Monitor

Published before and after this one in the same product

← EarlierCVE-2018-16837Oct 23, 2018 · Ansible "User" module leaks any data which is passed on as a parameter to ssh-keygen.
31Monitor
← EarlierCVE-2018-16859Nov 29, 2018 · Execution of Ansible playbooks on Windows platforms with PowerShell ScriptBlock logging and Module logging enabled can allow for 'become' pa
17Monitor
Later →CVE-2020-1734Mar 3, 2020 · A flaw was found in the pipe lookup plugin of ansible.
29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
alpine:ansible	2.8.6-r0 · Alpine:v3.10	Package registry (OSV)
alpine:ansible-base	2.8.6-r0 · Alpine:v3.13	Package registry (OSV)
debian:ansible	2.8.6+dfsg-1 · Debian:12	Package registry (OSV)
opensuse:ansible	2.9.6-lp151.2.7.1 · openSUSE:Leap 15.1	Package registry (OSV)
opensuse:ansible-10	10.6.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:ansible-11	11.11.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:ansible-12	12.2.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:ansible-13	13.7.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:ansible-9	9.8.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
PyPI:ansible	2.6.20	Package registry (OSV)
PyPI:ansible	2.7.14	Package registry (OSV)
PyPI:ansible	2.8.1	Package registry (OSV)
PyPI:ansible	2.8.6	Package registry (OSV)
PyPI:ansible	2.9.0rc4	Package registry (OSV)
red hat:ansible	0:2.6.20-1.el7ae · Red Hat:ansible_engine:2.6::el7	Package registry (OSV)
suse:ansible	2.9.6-bp151.3.6.1 · SUSE:Package Hub 15 SP1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-117 · Improper Output Neutralization for Logs

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.html

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records