# CVE-2026-16222: 1Panel-dev CordysCRM Third Party Endpoint TokenService.java server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in CordysCRM's TokenService to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-pg8h-hjrw-38c4

## What is CVE-2026-16222?

CVE-2026-16222 is a medium-severity server-side request forgery vulnerability in 1Panel-dev CordysCRM, published on 19 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in 1Panel-dev CordysCRM up to 1.4.1. This issue affects some unknown processing of the file backend/crm/src/main/java/cn/cordys/crm/integration/sso/service/TokenService.java of the component Third Party Endpoint. Performing a manipulation of the argument mkAddress results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could be used. The project closed the issue report, stating that this is not the official way to report a security vulnerability.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-16222 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16222 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16222 is a medium-severity server-side request forgery vulnerability in 1Panel-dev CordysCRM, published on 19 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16222 exists.

Affected product: 1Panel-dev CordysCRM. 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-16222/ (Markdown: https://insights.sbomify.com/CVE-2026-16222/index.md)
```

## Sources

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

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