# CVE-2026-120200: Nexterm through 1.2.2-BETA Missing Authorization in Server Session Lifecycle Routes


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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-qprx-3355-vjrx

## What is CVE-2026-120200?

CVE-2026-120200 is a medium-severity vulnerability in gnmyt Nexterm, published on 31 Oct 2026. 

### Official description

Nexterm through 1.2.2-BETA contains a missing authorization vulnerability that allows authenticated users to hibernate, resume, or terminate other users' remote sessions via session lifecycle routes. Attackers who obtain a session ID can call the hibernate, resume, or DELETE connection endpoints to disrupt live SSH, RDP, VNC, or SFTP sessions.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-120200 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120200 is a medium-severity vulnerability in gnmyt Nexterm, published on 31 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-120200 in the wild and no public exploit code.

Affected product: gnmyt Nexterm. 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-120200/ (Markdown: https://insights.sbomify.com/CVE-2026-120200/index.md)
```

## Sources

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

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