Cross-workspace repository access via unchecked ownership
Published Sep 15, 2026 · Updated Sep 15, 2026
Broken access control in Dromara Jpom 2.11.12 and earlier allows remote authenticated users to access other workspaces' repositories. The /build/branch-list endpoint resolves a supplied repositoryId without verifying workspace ownership, then runs git ls-remote with the repository's stored credentials. Any authenticated account can enumerate repository existence and type and cause credential-bearing access to repositories assigned to another workspace.
Summary
What happened
Broken access control in Dromara Jpom 2.11.12 and earlier allows remote authenticated users to access other workspaces' repositories. The /build/branch-list endpoint resolves a supplied repositoryId without verifying workspace ownership, then runs git ls-remote with the repository's stored credentials. Any authenticated account can enumerate repository existence and type and cause credential-bearing access to repositories assigned to another workspace.
The record
- CVE
- CVE-2026-91993
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Dromara
- Product
- Jpom
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.11.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo