# CVE-2026-19391: Information disclosure in Pen Drive Powered by Red Hat Lightspeed

> Insufficient credential redaction in insights-core exposes SSSD and Pacemaker passwords in uploaded archives, allowing attackers to read sensitive credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-2pq5-gq5q-3g2p

## What is CVE-2026-19391?

CVE-2026-19391 is a medium-severity vulnerability in Pen Drive Powered by Red Hat Lightspeed, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in insights-core where the password redaction layer fails to recognize credentials not keyed under the literal string 'password'. This allows SSSD LDAP bind passwords (ldap_default_authtok) and Pacemaker fence device credentials to be included in cleartext in archives uploaded to console.redhat.com.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-19391 being exploited?

There is no known exploitation of CVE-2026-19391 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19391 is a medium-severity vulnerability in Pen Drive Powered by Red Hat Lightspeed, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19391 in the wild and no public exploit code.

Affected product: Pen Drive Powered by Red Hat Lightspeed. 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-19391/ (Markdown: https://insights.sbomify.com/CVE-2026-19391/index.md)
```

## Sources

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

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