CVE-2026-91993
Received Received - Intake

Jpom Workspace Repository Access Vulnerability

Vulnerability report for CVE-2026-91993, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: VulnCheck

Description

Jpom through 2.11.12 fails to validate workspace ownership when resolving repositoryId on the /build/branch-list endpoint, allowing authenticated users to access repositories from other workspaces. Attackers can submit repository identifiers from different workspaces to enumerate repository existence, determine repository type, and execute git ls-remote commands using other workspaces' stored credentials.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
dromara jpom to 2.11.12 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-91993 is a medium-severity vulnerability in Jpom versions up to 2.11.12. It allows authenticated users to bypass workspace isolation by submitting repository identifiers from other workspaces to the /build/branch-list endpoint. This enables attackers to enumerate repository existence, determine repository type, and execute git ls-remote commands using credentials stored in other workspaces.

Detection Guidance

To detect this vulnerability, check if your Jpom instance (version <= 2.11.12) allows unauthorized access to the /build/branch-list endpoint. Use curl to test repository enumeration by sending requests with different repositoryId values across workspaces. Example: curl -X GET 'http://<target>/build/branch-list?repositoryId=<uuid>' with valid authentication headers.

Impact Analysis

This vulnerability allows unauthorized access to repositories in other workspaces, potentially exposing sensitive repository metadata and enabling attackers to validate stored credentials without direct access. It could lead to information disclosure and unauthorized actions if combined with other vulnerabilities.

Mitigation Strategies

Upgrade Jpom to a patched version beyond 2.11.12. If upgrading is not immediately possible, restrict access to the /build/branch-list endpoint via network controls or authentication policies. Review logs for suspicious repositoryId enumeration attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-91993. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart