Skip to main content
Menu
CVEs

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.

CVE-2026-130160EUVD-2026-130530Published November 19, 2026, updated

8.8HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 5.13.3
Who is exposed
Specific setups only

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

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

Who should check

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

“The "delete GPG key" action passes an attacker-controlled key ID straight into a shell command”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Any logged-in user can reach the GPG key delete action, since no authorization check beyond login is performed. The bug is reached through the GPG keys page under Repositories, by deleting a key.
  2. Upgrade 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-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"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 40 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lbr38/repomanager · Advisory GHSA-c78w-g4rj-q6q7
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130160
RecordNVD · CVE-2026-130160
Other links 3
RepositoryGitHub · lbr38/repomanager · Pull request #403
RepositoryGitHub · lbr38/repomanager · Commit d380579c
RepositoryGitHub · lbr38/repomanager · Release 5.13.3

Questions about CVE-2026-130160

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: cve.now feed data

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: github.com

Which versions are affected by CVE-2026-130160?

repomanager: before 5.13.3.

Source: cve.now feed data

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: github.com

How do I fix CVE-2026-130160?

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

Source: github.com

No corrections so far. Something wrong on this page? Report an error.