Quick answers
- Is CVE-2026-11819 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11819 being exploited in the wild.
- How severe is CVE-2026-11819?
- Medium severity, with a CVSS score of 5.5, published 23 June 2026.
- Which products and versions are affected?
- Ansible community.general v13.0.0; Red Hat Red Hat Enterprise Linux 8; Red Hat Red Hat Enterprise Linux 9; Red Hat Red Hat Enterprise Linux 10.
- Is there a fix for CVE-2026-11819?
- 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-11819 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-11819?
- Check whether you run Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 9. 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 keyring_info.py module in the Ansible community.general collection (v13.0.0) contains an information disclosure vulnerability (CWE-532). While the module correctly uses no_log=True for input parameters, it fails to apply similar protections to the returned result["passphrase"] field. An attacker with local access to Ansible job logs, fact caches (such as Redis or Memcached), or AWX/Tower history can retrieve sensitive credentials in plaintext. The vulnerability affects systems using GNOME Keyring, macOS Keychain, and Windows Credential Manager. A fix involves setting _ansible_no_log=True in the module's exit_json call and updating documentation to recommend task-level no_log usage.
Affected products
- Ansible community.general v13.0.0
- Red Hat Red Hat Enterprise Linux 8
- Red Hat Red Hat Enterprise Linux 9
- Red Hat Red Hat Enterprise Linux 10
Timeline
- 2026-06-09: disclosed: Initial report to Red Hat Bugzilla
- 2026-06-23: advisory: NVD and Red Hat published advisory details