# CVE-2026-95521: Rpm: rpm: shell command injection via macro expansion of source/spec file basenames when installing a source rpm

> Attackers can execute arbitrary shell commands by installing a malicious source RPM, affecting users of Red Hat Enterprise Linux and related distributions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** AZL-105326, DEBIAN-CVE-2026-95521, ECHO-1ff4-ea0c-39f6, GHSA-7prr-g333-3h48, UBUNTU-CVE-2026-95521

## What is CVE-2026-95521?

CVE-2026-95521 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 24 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 command injection flaw was found in rpm. Installing or rebuilding a source RPM whose source or spec file basenames contain a %() macro construct causes rpm to execute an attacker-controlled shell command via popen() while relocating the source file list. This allows arbitrary command execution as the invoking (typically non-root) user, simply by installing, rebuilding, or otherwise processing an untrusted .src.rpm.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-95521 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95521 is a high-severity command injection vulnerability in Red Hat Enterprise Linux 10, published on 24 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: There is no known exploitation of CVE-2026-95521 in the wild and no public exploit code.

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-95521/ (Markdown: https://insights.sbomify.com/CVE-2026-95521/index.md)
```

## Sources

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

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