CVE-2018-10855: 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.
Noroxi assessment
Priority: Monitor (action score 24/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: 3% (FIRST EPSS); higher than 87.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: ansible (Alpine:v3.7) 2.4.6.0-r0; ansible (Debian:12) 2.5.5+dfsg-1; ansible (Debian:9) 2.2.1.0-2+deb9u1.
Low priority for now. Upgrade to ansible (Alpine:v3.7) 2.4.6.0-r0; ansible (Debian:12) 2.5.5+dfsg-1; ansible (Debian:9) 2.2.1.0-2+deb9u1 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
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.
- BDU:2019-00887
- GHSA-jwcc-j78w-j73w
- DSA-4396-1
- openSUSE-SU-2019:0238-1
- openSUSE-SU-2024:14244-1
- openSUSE-SU-2024:14536-1
- openSUSE-SU-2025:15605-1
- openSUSE-SU-2025:15753-1
- openSUSE-SU-2026:10944-1
- openSUSE-SU-2026:12447-1
- PYSEC-2018-42
- RHBA-2018:3788
- RHSA-2018:1948
- RHSA-2018:1949
- RHSA-2018:2022
- RHSA-2018:2079
- RHSA-2018:2184
- RHSA-2018:2585
- RHSA-2019:0054
- SUSE-SU-2018:4130-1
- Published
- Jul 2, 2018
- Updated
- Jun 16, 2026
- EPSS
- 3.0% · 87th percentile
- CWE
- CWE-532
Report tools
Action score
24
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.0%
CNA vs NVD score
- NVD
- 5.9
- CNA · redhat
- 5.9
- agree
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 | cloudforms | cpe:2.3:a:redhat:cloudforms |
| redhat | openstack | cpe:2.3:a:redhat:openstack |
| redhat | virtualization | cpe:2.3:a:redhat:virtualization |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
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.
[UNKNOWN] ansible
- Ansible 2.4.5, Ansible 2.5.5affected
Affected versions · NVD (12)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.04
- debian debian linux9.0
- redhat ansible engineafter 2.5 · up to 2.5.5 inclusive
- redhat ansible engine2.4 and later · before 2.4.5
- redhat ansible engine2.0
- redhat cloudforms4.6
- redhat openstack10
- redhat openstack12
- redhat openstack13
- redhat virtualization4.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.7 | ansible | before 2.4.6.0-r0 | 2.4.6.0-r0 |
| Debian:12 | ansible | before 2.5.5+dfsg-1 | 2.5.5+dfsg-1 |
| Debian:9 | ansible | before 2.2.1.0-2+deb9u1 | 2.2.1.0-2+deb9u1 |
| 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-14 | before 14.6.0-1.1 | 14.6.0-1.1 |
| openSUSE:Tumbleweed | ansible-9 | before 9.8.0-1.1 | 9.8.0-1.1 |
| PyPI | ansible | from 2.4 · before 2.4.5.0 | 2.4.5.0 |
| PyPI | ansible | from 2.4.0.0 · before 2.4.5.0 | 2.4.5.0 |
| PyPI | ansible | from 2.5 · before 2.5.5 | 2.5.5 |
| PyPI | ansible | from 2.5.0a1 · before 2.5.5 | 2.5.5 |
| Red Hat:ansible_engine:2::el7 | ansible | before 0:2.5.5-1.el7ae | 0:2.5.5-1.el7ae |
| Red Hat:ansible_engine:2::el7 | ansible-doc | before 0:2.5.5-1.el7ae | 0:2.5.5-1.el7ae |
| Red Hat:ansible_engine:2.4::el7 | ansible | before 0:2.4.5.0-1.el7ae | 0:2.4.5.0-1.el7ae |
| Red Hat:ansible_engine:2.4::el7 | ansible-doc | before 0:2.4.5.0-1.el7ae | 0:2.4.5.0-1.el7ae |
| Red Hat:cloudforms_managementengine:5.9::el7 | ansible-tower | before 0:3.2.5-1.el7at | 0:3.2.5-1.el7at |
| Red Hat:cloudforms_managementengine:5.9::el7 | ansible-tower-server | before 0:3.2.5-1.el7at | 0:3.2.5-1.el7at |
| Red Hat:cloudforms_managementengine:5.9::el7 | ansible-tower-setup | before 0:3.2.5-1.el7at | 0:3.2.5-1.el7at |
| Red Hat:cloudforms_managementengine:5.9::el7 | ansible-tower-ui | before 0:3.2.5-1.el7at | 0:3.2.5-1.el7at |
| Red Hat:cloudforms_managementengine:5.9::el7 | ansible-tower-venv-ansible | before 0:3.2.5-1.el7at | 0:3.2.5-1.el7at |
| Red Hat:cloudforms_managementengine:5.9::el7 | ansible-tower-venv-tower | before 0:3.2.5-1.el7at | 0:3.2.5-1.el7at |
| Red Hat:cloudforms_managementengine:5.9::el7 | cfme | before 0:5.9.3.4-1.el7cf | 0:5.9.3.4-1.el7cf |
+19
Same product
redhat: all recordsOther 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…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…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-10874Jul 2, 2018 · In ansible it was found that inventory variables are loaded from current working directory when running ad-hoc command which are under…31Monitor
- Later →CVE-2018-10875Jul 13, 2018 · A flaw was found in ansible.31Monitor
- Later →CVE-2016-8647Jul 26, 2018 · An input validation vulnerability was found in Ansible's mysql_user module before 2.2.1.0, which may fail to correctly change a password in…19Monitor
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.4.6.0-r0 · Alpine:v3.7 | Package registry (OSV) |
| debian:ansible | 2.5.5+dfsg-1 · Debian:12 | 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-14 | 14.6.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-9 | 9.8.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:ansible | 2.4.5.0 | Package registry (OSV) |
| PyPI:ansible | 2.5.5 | Package registry (OSV) |
| red hat:ansible | 0:2.4.6.0-1.el7ae · Red Hat:openstack:12::el7 | Package registry (OSV) |
| red hat:ansible-doc | 0:2.5.5-1.el7ae · Red Hat:ansible_engine:2::el7 | Package registry (OSV) |
| red hat:ansible-role-redhat-subscription | 0:1.0.1-4.el7ost · Red Hat:openstack:12::el7 | Package registry (OSV) |
| red hat:ansible-tower | 0:3.2.5-1.el7at · Red Hat:cloudforms_managementengine:5.9::el7 | Package registry (OSV) |
| red hat:ansible-tower-server | 0:3.2.5-1.el7at · Red Hat:cloudforms_managementengine:5.9::el7 | Package registry (OSV) |
| red hat:ansible-tower-setup | 0:3.2.5-1.el7at · Red Hat:cloudforms_managementengine:5.9::el7 | Package registry (OSV) |
| red hat:imgbased | 0:1.0.20-0.1.el7ev · Red Hat:enterprise_linux:7::hypervisor | Package registry (OSV) |
| red hat:python-imgbased | 0:1.0.20-0.1.el7ev · Red Hat:enterprise_linux:7::hypervisor | Package registry (OSV) |
| red hat:redhat-release-virtualization-host | 0:4.2-4.3.el7 · Red Hat:enterprise_linux:7::hypervisor | Package registry (OSV) |
| red hat:redhat-virtualization-host | 0:4.2-20180622.0.el7_5 · Red Hat:enterprise_linux:7::hypervisor | Package registry (OSV) |
| red hat:redhat-virtualization-host-image-update | 0:4.2-20180622.0.el7_5 · Red Hat:enterprise_linux:7::hypervisor | Package registry (OSV) |
| red hat:redhat-virtualization-host-image-update-placeholder | 0:4.2-4.3.el7 · Red Hat:enterprise_linux:7::hypervisor | Package registry (OSV) |
| suse:ansible | 2.4.6.0-3.3.1 · SUSE:HPE Helion OpenStack 8 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- access.redhat.com/errata/RHSA-2018:1948
- access.redhat.com/errata/RHSA-2018:1949
- access.redhat.com/errata/RHSA-2018:2022
- access.redhat.com/errata/RHSA-2018:2079
- access.redhat.com/errata/RHSA-2018:2184
- access.redhat.com/errata/RHSA-2018:2585
- access.redhat.com/errata/RHSA-2019:0054
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10855
- usn.ubuntu.com/4072-1/
- www.debian.org/security/2019/dsa-4396
Vendor advisories and official records. Exploit/PoC links are deliberately left out.