Jpom through 2.11.12 Cross-Workspace Authorization Bypass via Docker Controllers
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Jpom v2.11.12 (the advisory reports this version).
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Jpom through 2.11.12 contains a cross-workspace authorization bypass vulnerability that allows authenticated users to manage other workspaces' Docker hosts by supplying foreign Docker asset ids. Attackers with Docker permission in any workspace can control containers, images, volumes and networks, including creating privileged containers with host bind mounts.
What to do
Check whether your setup matches what the bug needs.
Affects Jpom v2.11.12 (the advisory reports this version).Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- dromara Jpom
through 2.11.12
Evidence 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120460
What does this mean?
The title describes an authorization bypass across workspaces through Docker controllers in Jpom, so one workspace's boundary can be crossed through that feature. The checked facts do not describe the exact mechanism or its impact.Source: github.com
Am I affected, and how do I check?
The product range runs from the earliest release through Jpom 2.11.12, and the advisory reports v2.11.12 specifically. To check a installation, look up the Jpom version it runs and compare it with 2.11.12.Source: github.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be confirmed here. Check the dromara/Jpom release notes for a version later than 2.11.12 and upgrade to it once published.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data