Quick answers
- Is CVE-2026-80158 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-80158 being exploited in the wild.
- How severe is CVE-2026-80158?
- Medium severity, with a CVSS score of 5.5, published 26 August 2026.
- Which products and versions are affected?
- Ansible community.general <UNKNOWN>.
- Is there a fix for CVE-2026-80158?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-80158 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-80158?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The ipa_getkeytab module in community.general Ansible collection contains a credential disclosure vulnerability (CWE-214) in which the bind_pw parameter lacks the no_log attribute. This causes the LDAP simple-bind password to be recorded in cleartext across multiple locations: system journal/syslog output, module return values, verbose command output, and Automation Controller/AWX job logs. Additionally, the password is exposed on the command line as --bindpw argument to the ipa-getkeytab helper binary, making it visible to local users viewing the process table while the command executes. An authenticated local attacker (privilege required: low) with access to logs or the process list can extract the directory bind credential and potentially compromise IPA/LDAP accounts and resources that credential can access. Fix availability depends on Ansible project's patch release schedule.
Affected products
- Ansible community.general <UNKNOWN>
Timeline
- 2026-08-26: disclosed
- other: CVE-2026-80158 assigned