A flaw was found in ansible.
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.34% (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.19-r0; ansible (Alpine:v3.11) 2.9.18-r0; ansible (Alpine:v3.13) 2.10.7-r0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to ansible (Alpine:v3.10) 2.8.19-r0; ansible (Alpine:v3.11) 2.9.18-r0; ansible (Alpine:v3.13) 2.10.7-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 flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credentials. The highest threat from this vulnerability is to data confidentiality. Versions before ansible 2.9.18 are affected.
- Published
- May 26, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-532
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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
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 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 |
|---|---|---|
| oracle | virtualization | cpe:2.3:a:oracle:virtualization |
| redhat | ansible | cpe:2.3:a:redhat:ansible |
| redhat | ansible tower | cpe:2.3:a:redhat:ansible_tower |
| redhat | cisco nx-os collection | cpe:2.3:a:redhat:cisco_nx-os_collection |
| redhat | community general collection | cpe:2.3:a:redhat:community_general_collection |
| redhat | community network collection | cpe:2.3:a:redhat:community_network_collection |
| redhat | docker community collection | cpe:2.3:a:redhat:docker_community_collection |
| redhat | google cloud platform ansible collection | cpe:2.3:a:redhat:google_cloud_platform_ansible_collection |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- oracle virtualization4.0
- redhat ansiblebefore 2.8.19
- redhat ansible2.9.0 and later · before 2.9.18
- redhat ansible2.10.0 and later · before 2.10.7
- redhat ansible tower3.0
- redhat cisco nx-os collectionbefore 1.4.0
- redhat community general collectionbefore 1.3.6
- redhat community general collection2.0.0 and later · before 2.0.1
- redhat community network collectionbefore 1.3.2
- redhat community network collection2.0.0 and later · before 2.0.1
- redhat docker community collectionbefore 1.2.2
- redhat google cloud platform ansible collection1.0.2
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.
n/a ansible
- ansible 2.9.18affected
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 | from 2.9.0 · before 2.8.19-r0 | 2.8.19-r0 |
| Alpine:v3.11 | ansible | from 2.9.0 · before 2.9.18-r0 | 2.9.18-r0 |
| Alpine:v3.13 | ansible | from 2.9.0 · before 2.10.7-r0 | 2.10.7-r0 |
| Debian:10 | ansible | before 2.7.7+dfsg-1+deb10u2 | 2.7.7+dfsg-1+deb10u2 |
| Debian:12 | ansible | before 2.10.7-1 | 2.10.7-1 |
| openSUSE:Leap 15.4 | wire | before 0.5.0-150000.1.6.1 | 0.5.0-150000.1.6.1 |
| PyPI | ansible | from 2.10.0 · before 2.10.7 | 2.10.7 |
| PyPI | ansible | from 2.10.0a1 · before 2.10.7 | 2.10.7 |
| PyPI | ansible | from 2.9.0 · before 2.9.18 | 2.9.18 |
| PyPI | ansible | from 2.9.0a1 · before 2.9.18rc1 | 2.9.18rc1 |
| PyPI | ansible | before 2.8.19rc1 | 2.8.19rc1 |
| PyPI | ansible | before 2.8.19 | 2.8.19 |
| Red Hat:ansible_engine:2::el7 | ansible | before 0:2.9.18-1.el7ae | 0:2.9.18-1.el7ae |
| Red Hat:ansible_engine:2::el7 | ansible-test | before 0:2.9.18-1.el7ae | 0:2.9.18-1.el7ae |
| Red Hat:ansible_engine:2::el8 | ansible | before 0:2.9.18-1.el8ae | 0:2.9.18-1.el8ae |
| Red Hat:ansible_engine:2::el8 | ansible-test | before 0:2.9.18-1.el8ae | 0:2.9.18-1.el8ae |
| SUSE:HPE Helion OpenStack 8 | ansible | before 2.9.22-3.18.1 | 2.9.22-3.18.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | golang-github-prometheus-node_exporter | before 1.3.0-150000.3.15.1 | 1.3.0-150000.3.15.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | golang-github-prometheus-node_exporter | before 1.3.0-150000.3.15.1 | 1.3.0-150000.3.15.1 |
| SUSE:Manager Client Tools 15 | ansible | before 2.9.27-150000.1.14.1 | 2.9.27-150000.1.14.1 |
| SUSE:Manager Client Tools 15 | ansible | before 2.9.27-150000.1.14.1 | 2.9.27-150000.1.14.1 |
| SUSE:Manager Client Tools 15 | dracut-saltboot | before 0.1.1657643023.0d694ce-150000.1.35.1 | 0.1.1657643023.0d694ce-150000.1.35.1 |
| SUSE:Manager Client Tools 15 | dracut-saltboot | before 0.1.1657643023.0d694ce-150000.1.35.1 | 0.1.1657643023.0d694ce-150000.1.35.1 |
| SUSE:Manager Client Tools 15 | golang-github-QubitProducts-exporter_exporter | before 0.4.0-150000.1.15.1 | 0.4.0-150000.1.15.1 |
+38
Same product
oracle: all recordsOther highest-scoring records for the same primary product.
- CVE-2013-3779Unspecified vulnerability in the Secure Global Desktop component in Oracle Virtualization All 4.6 releases including 4.63 and 4.7 prior to 430Monitor
- CVE-2011-3538Unspecified vulnerability in the Sun Ray component in Oracle Virtualization 4.0 allows remote attackers to affect integrity, related to Auth28Monitor
- CVE-2015-2581Unspecified vulnerability in the Oracle Secure Global Desktop component in Oracle Virtualization 5.1 and 5.2 allows remote attackers to affe26Monitor
- CVE-2014-2439Unspecified vulnerability in the Oracle Secure Global Desktop (SGD) component in Oracle Virtualization 5.0 and 5.1 allows remote attackers t26Monitor
- CVE-2020-10775An Open redirect vulnerability was found in ovirt-engine versions 4.4 and earlier, where it allows remote attackers to redirect users to arb22Monitor
- CVE-2014-2475Unspecified vulnerability in the Oracle Secure Global Desktop component in Oracle Virtualization 4.63, 4.71, 5.0, and 5.1 allows remote atta21Monitor
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.19-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:ansible | 2.10.7-1 · Debian:12 | Package registry (OSV) |
| PyPI:ansible | 2.10.7 | Package registry (OSV) |
| PyPI:ansible | 2.8.19 | Package registry (OSV) |
| PyPI:ansible | 2.8.19rc1 | Package registry (OSV) |
| PyPI:ansible | 2.9.18 | Package registry (OSV) |
| PyPI:ansible | 2.9.18rc1 | Package registry (OSV) |
| red hat:ansible | 0:2.9.18-1.el7ae · Red Hat:ansible_engine:2::el7 | Package registry (OSV) |
| red hat:ansible-test | 0:2.9.18-1.el7ae · Red Hat:ansible_engine:2::el7 | Package registry (OSV) |
| suse:ansible | 2.9.22-3.18.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:ansible | 2.9.27-150000.1.14.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:dracut-saltboot | 0.1.1657643023.0d694ce-150000.1.35.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:golang-github-QubitProducts-exporter_exporter | 0.4.0-150000.1.15.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:mgr-daemon | 4.3.5-150000.1.35.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:mgr-virtualization | 4.3.6-150000.1.32.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:prometheus-blackbox_exporter | 0.19.0-150000.1.11.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:python-hwdata | 2.3.5-150000.3.9.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:spacecmd | 4.3.14-150000.3.83.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:spacewalk-client-tools | 4.3.11-150000.3.65.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:uyuni-common-libs | 4.3.5-150000.1.24.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:uyuni-proxy-systemd-services | 4.3.6-150000.1.6.1 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:zypp-plugin-spacewalk | 1.0.13-150000.3.32.1 · SUSE:Manager Client Tools 15 | 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.
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0441 · Jun 3, 2021(RedHat Güvenlik Güncellemesi Yayınladı)
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-532 · Insertion of Sensitive Information into Log FileCVSS 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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.