Skip to main content
VulnerabilityPublished

CVE-2026-130160: lbr38 repomanager · OS Command Injection

Affects lbr38 repomanagerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 5.13.3 soon.

Data as of 19 Nov 2026, 18:55 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
Patch
Available – fixed in 5.13.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade lbr38 repomanager to 5.13.3.

Affected software

ProductAffectedFixed in
lbr38repomanagerAffected
  • <5.13.3
Fixed in
  • 5.13.3

AI-suggested

Upgrade repomanager to version 5.13.3 or later, where this vulnerability is fixed. The fix ensures proper handling and sanitization of the GPG key identifier to prevent command injection. No additional mitigations are indicated by the vendor advisory. Since authentication is required, ensure that only trusted users have access to the affected functionality.

Description

CVE-2026-130160 is an OS command injection vulnerability in lbr38 repomanager versions prior to 5.13.3. An authenticated user can supply a crafted GPG key identifier to the key deletion action, which is not properly shell-encoded, allowing arbitrary OS command execution via the web/PHP process. The flaw exists because Validate::string() filters HTML but not shell metacharacters, and the vulnerable code path uses proc_open() with /bin/sh -c. The vulnerability requires authentication but does not strictly require administrator privileges. The issue is fixed in version 5.13.3.

References

Community reviews

Loading reviews…