CVE-2026-130158: RepoManager: Stored XSS via host-reported package metadata
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.13.3
Event History
Frequently Asked Questions
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.
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.
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.
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.