# CVE-2026-85013: Command injection in Red Hat Enterprise Linux 10

> Local attackers can execute arbitrary commands via shell metacharacters in module names during Bash completion, affecting Linux users.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** ALSA-2026:80664, ALSA-2026:82919, ALSA-2026:84594, AZL-107969, DEBIAN-CVE-2026-85013, RHSA-2026:64766, RHSA-2026:80664, RHSA-2026:82919, RHSA-2026:84594, RLSA-2026:80664, RLSA-2026:82919, RLSA-2026:84594, UBUNTU-CVE-2026-85013

## What is CVE-2026-85013?

CVE-2026-85013 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in environment-modules. A local attacker can exploit this vulnerability by placing a maliciously named modulefile in a location visible to the victim's `MODULEPATH`. When the victim uses Bash completion for `module` or `ml` commands, the malicious module name, containing shell metacharacters, is evaluated as a command. This can lead to arbitrary command execution in the completing user's shell, impacting their confidentiality, integrity, and availability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `environment-modules` | AlmaLinux:10 | All versions | 5.6.1-2.el10_2.1 |
| `environment-modules` | AlmaLinux:8 | All versions | 4.5.2-5.el8_10 |
| `environment-modules` | AlmaLinux:9 | All versions | 5.3.0-2.el9_8.1 |
| `environment-modules` | Red Hat:enterprise_linux:10.2 | All versions | 0:5.6.1-2.el10_2.1 |
| `environment-modules-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:5.6.1-2.el10_2.1 |
| `environment-modules-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:5.6.1-2.el10_2.1 |
| `environment-modules` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.5.2-5.el8_10 |
| `environment-modules-compat-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.5.2-5.el8_10 |
| `environment-modules-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.5.2-5.el8_10 |
| `environment-modules-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.5.2-5.el8_10 |
| `environment-modules` | Red Hat:enterprise_linux:9::baseos | All versions | 0:5.3.0-2.el9_8.1 |
| `environment-modules-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:5.3.0-2.el9_8.1 |
| `environment-modules-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:5.3.0-2.el9_8.1 |
| `environment-modules` | Red Hat:hummingbird:1 | All versions | 0:5.6.2-1.hum1 |
| `environment-modules` | Rocky Linux:10 | All versions | 0:5.6.1-2.el10_2.1 |
| `environment-modules` | Rocky Linux:8 | All versions | 0:4.5.2-5.el8_10 |
| `environment-modules` | Rocky Linux:9 | All versions | 0:5.3.0-2.el9_8.1 |

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

Apply the vendor's patch.

## Is CVE-2026-85013 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85013 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85013 exists.

Affected product: Red Hat Enterprise Linux 10. 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-85013/ (Markdown: https://insights.sbomify.com/CVE-2026-85013/index.md)
```

## Sources

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

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