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


- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-p83w-vf54-73v4

## What is CVE-2026-120209?

CVE-2026-120209 is a critical vulnerability in anji-plus AJ-Report, published on 31 Oct 2026. 

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-120209?


## How do I fix CVE-2026-120209?

No fix has been published for CVE-2026-120209 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120209 being exploited?

There is no known exploitation of CVE-2026-120209 in the wild and no public exploit code.

Public exploit code:

-  Doctreat Core <= 1.6.8 - Unauthenticated Privilege Escalation | RCE (github_poc): https://github.com/Nxploited/CVE-2026-120209

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120209 and fix it if it is affected.

What it is: CVE-2026-120209 is a critical vulnerability in anji-plus AJ-Report, published on 31 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-120209 in the wild and no public exploit code.

Affected product: anji-plus AJ-Report. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120209/ (Markdown: https://insights.sbomify.com/CVE-2026-120209/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120209
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120209
- OSV: https://osv.dev/vulnerability/CVE-2026-120209

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120209/
Summaries are generated and may contain mistakes; the official description above is the record.