CVE-2026-130160: RepoManager: Authenticated OS command injection (RCE) via GPG key deletion

Published Nov 19, 2026
·
Updated

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 procopen() 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.

Affected Software

0 affected components

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.13.3

Event History

Nov 19, 2026
CVE Published
via MITRE·06:42 PM
Data Sourced
via MITRE·06:42 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this vulnerability?

An authenticated RepoManager user can exploit it if they can invoke the GPG key deletion action. The advisory does not establish that administrator privileges are required; that depends on the deployment's intended access policy.

2

What does an attacker need to do to achieve code execution?

The attacker needs valid authentication and must submit a user-controlled, array-valued GPG key identifier to the key deletion action. Shell metacharacters in that identifier can reach /bin/sh -c without shell-safe encoding, enabling commands to run as the web/PHP process.

3

What is the immediate mitigation if upgrading is not possible?

Restrict access to the GPG key deletion action to only trusted users, or disable that action if possible. Because exploitation requires authentication, reducing who can access this functionality limits exposure.

4

How can I determine whether my instance is affected?

Instances running RepoManager versions earlier than 5.13.3 are affected if authenticated users can access the vulnerable GPG key deletion path in controllers/Gpg.php. Version 5.13.3 contains the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203