# CVE-2026-15584: Privilege escalation in Pen Drive Powered by Red Hat Lightspeed

> Attackers with edit role can exec into privileged debug pods to gain root access on cluster nodes, requiring immediate patching of the incluster-checks tool.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-r5gr-595c-57qv

## What is CVE-2026-15584?

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

### Official description

A privilege escalation vulnerability was found in the incluster-checks tool for OpenShift. The tool creates privileged debug pods with host filesystem access in the shared default namespace, where any user with the standard edit role can exec into them and obtain root access on cluster nodes.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2026-15584 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15584 is a high-severity vulnerability in Pen Drive Powered by Red Hat Lightspeed, published on 13 Jul 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-15584 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-15584/ (Markdown: https://insights.sbomify.com/CVE-2026-15584/index.md)
```

## Sources

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

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