CVE-2026-91993: Jpom through 2.11.12 Workspace Isolation Bypass via /build/branch-list

Published Sep 15, 2026
·
Updated

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.

Affected Software

1 affected component
Jpom<=2.11.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Jpom to a version that resolves this vulnerability.

    Fixed in 2.11.12
  2. Configuration

    Patch Jpom to enforce workspace ownership validation when resolving repositoryId on the /build/branch-list endpoint (the flaw affects versions through 2.11.12).

    Jpom /build/branch-list endpoint workspace ownership validation for repositoryId = enabled

Event History

Sep 15, 2026
CVE Published
via MITRE·11:35 AM
Data Sourced
via MITRE·11:35 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated Jpom user with privileges sufficient to call the /build/branch-list endpoint can exploit it. The attacker needs a repositoryId belonging to another workspace; the issue can also be used to enumerate whether such repositories exist.

2

What information or actions can an attacker obtain?

An attacker can determine the existence and type of repositories in other workspaces. They can also cause git ls-remote commands to run using credentials stored by the affected workspace, potentially exposing remote repository branch or reference information.

3

Are deployments affected by default?

The provided information confirms the issue affects Jpom through 2.11.12, but does not state whether the endpoint is enabled or reachable in a default deployment. Exploitation requires an authenticated account and access to the affected endpoint.

4

How can I check for exposure?

Review access to /build/branch-list and identify authenticated users who can submit repositoryId values. Test whether a user in one workspace can supply a repositoryId from another workspace and receive repository existence, type, or remote-reference results.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203