CVE-2026-95521

HIGH
Published September 24, 2026

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...

Full CISO analysis pending enrichment.

What systems are affected?

PackageEcosystemVulnerable RangePatched
MLflowpip—No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago20% patched~68d to patchFull package profile →
MLflowpip—No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago20% patched~68d to patchFull package profile →
MLflowpip—No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago20% patched~68d to patchFull package profile →
rhoai/odh-ai-gateway-operator-rhel9——No patch
rhoai/odh-core-bff-rhel9——No patch
rhoai/odh-dashboard-operator-rhel9——No patch
rhoai/odh-dashboard-rhel9——No patch
rhoai/odh-data-science-pipelines-operator-controller-rhel9——No patch
rhoai/odh-kf-notebook-controller-rhel9——No patch
rhoai/odh-kserve-controller-rhel9——No patch
rhoai/odh-kserve-llmisvc-controller-rhel9——No patch
rhoai/odh-kserve-module-operator-rhel9——No patch
rhoai/odh-kube-rbac-proxy-rhel9——No patch
rhoai/odh-kuberay-operator-controller-rhel9——No patch
rhoai/odh-llama-stack-k8s-operator-rhel9——No patch
rhoai/odh-maas-controller-rhel9——No patch
rhoai/odh-mod-arch-agent-ops-rhel9——No patch
rhoai/odh-mod-arch-automl-rhel9——No patch
rhoai/odh-mod-arch-autorag-rhel9——No patch
rhoai/odh-mod-arch-eval-hub-rhel9——No patch
rhoai/odh-mod-arch-gen-ai-rhel9——No patch
rhoai/odh-mod-arch-maas-rhel9——No patch
rhoai/odh-mod-arch-model-registry-rhel9——No patch
rhoai/odh-model-controller-rhel9——No patch
rhoai/odh-model-registry-operator-rhel9——No patch
rhoai/odh-model-serving-api-rhel9——No patch
rhoai/odh-notebook-controller-rhel9——No patch
rhoai/odh-ogx-k8s-operator-rhel9——No patch
rhoai/odh-ogx-module-operator-rhel9——No patch
rhoai/odh-training-operator-rhel9——No patch
rhoai/odh-trustyai-service-operator-rhel9——No patch
rhoai/odh-workbenches-operator-rhel9——No patch
rpm——No patch

How severe is it?

CVSS 3.1
7.8 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
N/A

What is the attack surface?

AVACPRUISCIA
AVLocal
ACLow
PRNone
UIRequired
SUnchanged
CHigh
IHigh
AHigh

What should I do?

No patch available

Monitor for updates. Consider compensating controls or temporary mitigations.

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-95521?

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.

Is CVE-2026-95521 actively exploited?

No confirmed active exploitation of CVE-2026-95521 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-95521?

No patch is currently available. Monitor vendor advisories for updates.

What is the CVSS score for CVE-2026-95521?

CVE-2026-95521 has a CVSS v3.1 base score of 7.8 (HIGH).

What are the technical details?

Original Advisory

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.

Weaknesses (CWE)

CWE-78 — Improper Neutralization of Special Elements used in an OS Command: The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component.

  • [Architecture and Design] If at all possible, use library calls rather than external processes to recreate the desired functionality.
  • [Architecture and Design, Operation] Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

References

Timeline

Published
September 24, 2026
Last Modified
November 6, 2026
First Seen
November 6, 2026

Related Vulnerabilities