Quick answers
- Is CVE-2026-91993 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91993 being exploited in the wild.
- How severe is CVE-2026-91993?
- Medium severity, with a CVSS score of 4.3, published 15 September 2026.
- Which products and versions are affected?
- Dromara Jpom through 2.11.12.
- Is there a fix for CVE-2026-91993?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-91993 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-91993?
- Check whether you run Dromara Jpom at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in the /build/branch-list endpoint that fails to validate workspace ownership when resolving repositoryId parameters. An authenticated user can submit repository identifiers from different workspaces to enumerate repository existence, determine repository type, and execute git ls-remote commands using stored credentials from those other workspaces. The attack requires authentication but does not require additional user interaction. An attacker can discover repositories across workspaces and potentially extract sensitive information from repository configurations or credentials. The flaw affects Jpom through version 2.11.12; patches for later versions should be available.
Affected products
- dromara Jpom through 2.11.12
Timeline
- 2026-09-15: disclosed