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.

Attack Vector Network

Attack Complexity Low

Privileges Required Low

Attack Requirements None

User Interaction None

Vulnerable System Confidentiality Impact Low

Vulnerable System Integrity Impact None

Vulnerable System Availability Impact None

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

Attack Vector Network

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact Low

Integrity Impact None

Availability Impact None

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
dromara Jpom unaffected
Version Status Constraints
0 affected ≤ 2.11.12

No data.

No data.

No data.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://github.com/dromara/Jpom cve-icon cve-icon
https://github.com/dromara/Jpom/blob/v2.11.12/modules/server/src/main/java/org/dromara/jpom/controller/build/BuildInfoController.java#L436-L454 cve-icon cve-icon
https://github.com/dromara/Jpom/issues/115 cve-icon cve-icon
https://www.vulncheck.com/advisories/jpom-through-2.11.12-workspace-isolation-bypass-via-build-branch-list cve-icon cve-icon
History

Tue, 15 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
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.
Title Jpom through 2.11.12 Workspace Isolation Bypass via /build/branch-list
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-15T11:35:48.715Z

Reserved: 2026-09-15T11:11:13.311Z

Link: CVE-2026-91993

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-15T12:17:54.640

Modified: 2026-09-15T12:17:54.640

Link: CVE-2026-91993

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses