Skip to main content
Menu
CVEs

RepoManager arbitrary file read in unit logs

CVE-2026-130159Published November 19, 2026, updated

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 5.13.3
Who is exposed
Not reported

Summary

RepoManager, a self-hosted deb/rpm package repository, has a path traversal flaw in its service unit log viewer that lets a remote attacker with a low-privilege login read files outside the intended directory. An attacker can retrieve any file the www-data service account can read, including application configuration, source code, and the GPG signing-key passphrase.

Written by a model

Original description

RepoManager is a self-hosted deb/rpm package repository. Prior to 5.13.3, the authenticated get-unit-log action accepts a caller-controlled logfile value. Validate::string() escapes HTML but leaves path traversal components unchanged. The action joins the caller-controlled logfile to SERVICE_LOGS_DIR without enforcing containment, so traversal can resolve the file read outside that directory. www/controllers/ajax/status/service.php reads and returns the resolved file, and any authenticated user can invoke the action to retrieve files readable by the www-data service account, including application configuration, source code, and the GPG signing-key passphrase. Fixed in 5.13.3.

What to do

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-130159 (RepoManager: Authenticated Path Traversal allows arbitrary file read via service unit log viewer), 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-130159 (entry last updated 2026-11-19):
Affected:
- lbr38 repomanager: fixed in 5.13.3
Fixed versions: 5.13.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130159 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130159 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-vqjf-mvm9-x879
- 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-130159
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-130159"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

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

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lbr38/repomanager · Advisory GHSA-vqjf-mvm9-x879
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130159
RecordNVD · CVE-2026-130159
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-130159

Is CVE-2026-130159 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

Which versions are affected by CVE-2026-130159?

repomanager: before 5.13.3.

Source: cve.now feed data

How do I fix CVE-2026-130159?

Upgrade to a fixed version: 5.13.3.

Source: cve.now feed data

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