CVE-2026-130158: RepoManager: Stored XSS via host-reported package metadata

Published Nov 19, 2026
·
Updated

RepoManager is a self-hosted deb/rpm package repository. Prior to 5.13.3, a registered host or a party with its host/API credential can submit package metadata. Inventory reporting accepts package name and version, while available-update reporting accepts package name, version, and repository; the repository field exists only on that path. RepoManager stores these values, and stored values are rendered on the host's package detail page without preventing stored HTML or JavaScript from executing. An administrator must later view the page for script execution. The script runs in the administrator's authenticated browser session and can expose administrative data or forge privileged requests; the advisory describes possible escalation through admin-only functionality. Fixed in 5.13.3.

Affected Software

1 affected component
RepoManager RepoManager<5.13.3

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:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can submit the malicious metadata?

A registered host can submit it, as can anyone who possesses that host's API credential. Exploitation does not require an unauthenticated attacker, but it does require access to a registered host or its credential.

2

What must happen for the stored script to execute?

An administrator must open the affected host's package detail page after the malicious package metadata has been stored. The script then executes in that administrator's authenticated browser session.

3

Which reporting paths can carry the affected values?

Inventory reporting accepts package name and version. Available-update reporting accepts package name, version, and repository; the repository field is present only in the available-update path.

4

What is the remediation?

Upgrade RepoManager to version 5.13.3, which contains the fix. The affected versions are those prior to 5.13.3.

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