RepoManager remote code execution in RPM repository mirroring
Affects repomanager 5.13.2 and older on instances that mirror an RPM repository as a source. Fixed in 5.13.3.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.13.3
- Who is exposed
- Specific setups only
Summary
RepoManager, a self-hosted deb and rpm package repository tool, has a command injection flaw in how it mirrors RPM repositories. An attacker who controls an upstream RPM repository that the instance mirrors can, remotely and with low-privilege login, run commands as the www-data service account by putting shell metacharacters in a package filename in the primary.xml location field.
Written by a model
Original description
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.
Who should check
Teams running repomanager 5.13.2 or older that mirror RPM repositories with Check GPG signatures enabled, including RPM source repos from third parties.
“When mirroring an RPM repository, repomanager takes each package's filename”
What to do
Check whether your setup matches what the bug needs.
repomanager 5.13.2 or older is affected; fixed in 5.13.3 The instance mirrors an RPM repository as a source The mirrored upstream repository is controlled by the attackerUpgrade to a fixed version: 5.13.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130157 (RepoManager: Command injection (RCE) via unsanitized RPM package filename when mirroring a repository), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130157 (entry last updated 2026-11-19):
Affected:
- lbr38 repomanager: fixed in 5.13.3
Fixed versions: 5.13.3.
Conditions (all must be true for the bug to be hit):
- repomanager 5.13.2 or older is affected; fixed in 5.13.3 (source: https://github.com/lbr38/repomanager/security/advisories/GHSA-ph7j-x866-rc66)
- The instance mirrors an RPM repository as a source (source: https://github.com/lbr38/repomanager/security/advisories/GHSA-ph7j-x866-rc66)
- The mirrored upstream repository is controlled by the attacker (source: https://github.com/lbr38/repomanager/security/advisories/GHSA-ph7j-x866-rc66)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130157 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130157 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lbr38/repomanager/security/advisories/GHSA-ph7j-x866-rc66
- https://github.com/lbr38/repomanager/pull/403
- https://github.com/lbr38/repomanager/commit/d380579c84accf1786934deee245650bbc68a562
- https://github.com/lbr38/repomanager/releases/tag/5.13.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130157
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130157"}.Affected versions
- lbr38 repomanagerfixed in 5.13.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lbr38/repomanager · Advisory GHSA-ph7j-x866-rc66 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130157 |
| Record | NVD · CVE-2026-130157 |
| Other links 3 | |
| Repository | GitHub · lbr38/repomanager · Pull request #403 |
| Repository | GitHub · lbr38/repomanager · Commit d380579c |
| Repository | GitHub · lbr38/repomanager · Release 5.13.3 |
Questions about CVE-2026-130157
Is CVE-2026-130157 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
When mirroring an RPM repository, repomanager takes each package's filename from the upstream repository without sanitizing it. A crafted filename in an upstream repository that an attacker controls can inject commands, leading to remote code execution as www-data on the repomanager host.
Source: github.com
Which versions are affected by CVE-2026-130157?
repomanager: before 5.13.3.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 5.13.2 and older are affected, but only on instances that mirror an RPM repository as a source, and only when the mirrored upstream repository is controlled by an attacker. To check, look at the installed repomanager version and whether any configured mirror uses an RPM repository as its source.
Source: github.com
How do I fix CVE-2026-130157?
Upgrade repomanager to 5.13.3 or later, which is the fixed version.
Source: github.com
Related
- CVE-2026-130158RepoManager: Stored XSS via host-reported package metadata
- CVE-2026-130160RepoManager: Authenticated OS command injection (RCE) via GPG key deletion
- CVE-2026-130159RepoManager: Authenticated Path Traversal allows arbitrary file read via service unit log viewer
- CVE-2026-133323A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an…
- CVE-2026-129989Dokploy: OS Command Injection via unsanitized publishDirectory in Nixpacks build pipeline
- CVE-2026-129986Dokploy: OS Command Injection via filePath in mount.deleteFileMount → HOST RCE
No corrections so far. Something wrong on this page? Report an error.