# CVE-2026-11819: Community.general: community.general keyring_info — os keyring passphrase returned in plaintext

> The Ansible keyring_info module exposes retrieved passphrases in plaintext output, allowing attackers with log access to steal credentials.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-5x67-m8gc-wm3p

## What is CVE-2026-11819?

CVE-2026-11819 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-11819?

It affects 1 product.


Products: Redhat Enterprise Linux.

## How do I fix CVE-2026-11819?

No fix has been published for CVE-2026-11819 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11819 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11819 exists.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11819 and fix it if it is affected.

What it is: CVE-2026-11819 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11819 exists.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11819/ (Markdown: https://insights.sbomify.com/CVE-2026-11819/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11819
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11819
- OSV: https://osv.dev/vulnerability/CVE-2026-11819

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11819/
Summaries are generated and may contain mistakes; the official description above is the record.