Microsoft · Ansible-collection-community-general: community.general: ipa_getkeytab does not set no_log on the bind_pw parameter
Affects MicrosoftSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 17 Nov 2026, 12:34 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Ceph Storage 5 | Affected– | Fixed in– |
| Red HatRed Hat Ceph Storage 9 | Affected– | Fixed in– |
| Red HatRed Hat OpenStack Platform 17.1 | Affected– | Fixed in– |
| Red HatRed Hat OpenStack Platform 18.0 | Affected– | Fixed in– |
AI-suggested
Until a fix is available, users should avoid logging sensitive parameters or apply manual workarounds to prevent bind_pw from being logged. Monitor official Microsoft or Ansible community advisories for updates.
Description
The vulnerability in the Ansible collection community.general's ipa_getkeytab module involves the bind_pw parameter not having the no_log attribute set, potentially exposing sensitive password information in logs.