CVE-2026-130157: RepoManager: Command injection (RCE) via unsanitized RPM package filename when mirroring a repository
RepoManager is a self-hosted deb/rpm package repository. Prior to 5.13.3, an attacker who controls an upstream RPM repository mirrored by a RepoManager instance can provide a package filename through the primary.xml <location href> field; the mirror passes that filename into a shell-interpreted RPM query, allowing shell metacharacters to execute commands as the www-data service account. The target must mirror an upstream repository controlled by the attacker, and the default "Check GPG signatures" option triggers the vulnerable call. The command executes before a later signature-verification failure, so a valid signed package is not required. Fixed in 5.13.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.13.3
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
RepoManager instances before 5.13.3 are exposed when they mirror an upstream RPM repository controlled by an attacker. The vulnerable path is triggered by the default "Check GPG signatures" option.
What does an attacker need to exploit it?
The attacker needs control of an upstream RPM repository that the target RepoManager instance mirrors. They can place shell metacharacters in a package filename supplied through the primary.xml location href field.
Is a valid GPG-signed RPM required for exploitation?
No. The injected command runs before the later signature-verification failure, so the package does not need to be validly signed.
What privileges does the injected command receive?
Commands execute as the www-data service account.
What version fixes the issue?
Upgrade RepoManager to version 5.13.3.