RepoManager stored XSS in host-reported package metadata
Affects RepoManager before 5.13.3 when an administrator opens a host's package detail page in the web UI. Fixed in 5.13.3.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.13.3
- Who is exposed
- Specific setups only
Summary
RepoManager, a self-hosted deb/rpm package repository, stores package metadata reported by hosts without blocking embedded scripts. A registered host, or anyone holding its credential, can exploit this remotely over the network by submitting crafted package name, version, or repository values. When an administrator views that host's package detail page, the script runs in their logged-in browser session and can expose administrative data or forge privileged requests.
Written by a model
Original description
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.
Who should check
Teams running lbr38 RepoManager 5.13.2 or earlier, where hosts report installed or available packages through the agent API and admins view host pages.
“An authenticated host (or any principal holding a host/API credential) can store arbitrary HTML/JavaScript in a host's package inventory via the agent API.”
What to do
Check whether your setup matches what the bug needs.
An administrator must open the affected host's package detail page in the web UI for the stored payload to run.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-130158 (RepoManager: Stored XSS via host-reported package metadata), 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-130158 (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):
- An administrator must open the affected host's package detail page in the web UI for the stored payload to run. (source: https://github.com/lbr38/repomanager/security/advisories/GHSA-4766-qc2v-p59h)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-130158 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130158 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-4766-qc2v-p59h
- 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-130158
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-130158"}.Affected versions
- lbr38 repomanagerfixed in 5.13.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9/10CVSS 9.0
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lbr38/repomanager · Advisory GHSA-4766-qc2v-p59h |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130158 |
| Record | NVD · CVE-2026-130158 |
| Other links 3 | |
| Repository | GitHub · lbr38/repomanager · Pull request #403 |
| Repository | GitHub · lbr38/repomanager · Commit d380579c |
| Repository | GitHub · lbr38/repomanager · Release 5.13.3 |
Questions about CVE-2026-130158
Is CVE-2026-130158 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. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Package metadata reported by a managed host is stored and later runs as a script in the browser of an administrator who opens that host's package detail page in the web UI. The script runs in the administrator's authenticated session, so it can read admin-visible data and forge admin actions.
Source: github.com
Which versions are affected by CVE-2026-130158?
repomanager: before 5.13.3.
Source: cve.now feed data
Am I affected, and how do I check?
RepoManager versions before 5.13.3 are listed as affected. To check an installation, compare the installed RepoManager version with 5.13.3. The issue requires an administrator to open the affected host's package detail page in the web UI.
Source: github.com
How do I fix CVE-2026-130158?
Upgrade RepoManager to 5.13.3 or later, the listed fixed version.
Source: github.com
Related
- CVE-2026-130160RepoManager: Authenticated OS command injection (RCE) via GPG key deletion
- CVE-2026-130157RepoManager: Command injection (RCE) via unsanitized RPM package filename when mirroring a repository
- CVE-2026-130159RepoManager: Authenticated Path Traversal allows arbitrary file read via service unit log viewer
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-131260Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.