VulnerabilityPublished 23 Jun 2026Updated 5 Nov 2026

CVE-2026-11819: Red Hat Enterprise Linux 10 · Sensitive Data in Logs

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 5 Nov 2026, 16:49 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	5.5

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jun 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 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-532

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10rhel-system-roles	Affected–	Fixed in–
Red Hat Enterprise Linux 8rhc-worker-playbook	Affected–	Fixed in–
Red Hat Enterprise Linux 8rhel-system-roles	Affected–	Fixed in–
Red Hat Enterprise Linux 9rhel-system-roles	Affected–	Fixed in–

AI-suggested

Meanwhile, users should apply no_log: true at the task level when using the affected module to prevent sensitive passphrases from being logged or cached. The vendor advisory suggests modifying the module to use _ansible_no_log=True on output to suppress sensitive information. Follow official Red Hat guidance at https://access.redhat.com/security/cve/CVE-2026-11819 for updates and remediation instructions.

Description

Module: plugins/modules/keyring_info.py CVSS 3.1: 5.5 MEDIUM — AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Issue: The module retrieves a passphrase from the OS native keyring (GNOME Keyring, macOS Keychain, Windows Credential Manager) and places it directly into result["passphrase"] with no output suppression, no no_log protection, and no documentation warning. Root Cause: Line 105 (protected): keyring_password=dict(type="str", required=True, no_log=True) Line 127 (NOT protected): result["passphrase"] = passphrase Observed Output: { "changed": false, "passphrase": "MyMasterP@ssw0rd!SSH_Key_Secret" } Visible via register + debug: { "keyring_result": { "changed": false, "passphrase": "MyMasterP@ssw0rd!SSH_Key_Secret" } } Impact: Master passwords, SSH key passphrases and service credentials appear in all Ansible output register: keyring_result followed by debug: var=keyring_result prints passphrase in full Ansible fact caching backends (Redis, JSON file, memcached) may persist the passphrase AWX/Tower job logs silently store the live credential Fix: module.exit_json(changed=False, passphrase=passphrase, _ansible_no_log=True) Also add a documentation warning requiring callers to use no_log: true at the task level. PoCs Fig 1: PoC execution showing passphrase in plaintext output Fig 2: Source code showing no_log=True on input (line 105) vs unprotected output (line 127)

Impact

Sensitive credentials such as master passwords and SSH key passphrases can be exposed in Ansible outputs, debug logs, fact caching backends, and AWX/Tower job logs. This exposure compromises confidentiality but does not affect integrity or availability. The leakage can lead to unauthorized access if logs or caches are accessed by unauthorized parties.

Summary

The vulnerability exists in the Ansible module plugins/modules/keyring_info.py used in Red Hat Enterprise Linux 10. It improperly outputs sensitive passphrases retrieved from OS native keyrings (GNOME Keyring, macOS Keychain, Windows Credential Manager) directly into the result dictionary without no_log protection. This causes the passphrase to be visible in Ansible output, debug registers, fact caches (such as Redis, JSON file, memcached), and AWX/Tower job logs. The root cause is that while the input parameter is marked with no_log=True, the output passphrase is not protected, leading to unintended exposure of sensitive information. The vulnerability has a CVSS 3.1 score of 5.5 (medium) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. The vendor advisory does not explicitly confirm a patch or remediation level but suggests a fix involving adding _ansible_no_log=True on module exit and documenting the need for no_log at the task level.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2026, 12:28 UTC

Technical details

References

Community reviews

Related threats