Nexterm through 1.2.2-BETA Missing Authorization in Server Session Lifecycle Routes
Affects Nexterm from 1.0.6-OPEN-PREVIEW through 1.2.2-BETA. CVSS scores it 5.3 (medium), and no vendor severity or fixed version is listed in the checked facts.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Nexterm, a remote server management application, is affected by this flaw. An authenticated user can pause, resume, or end other users' live remote sessions, such as SSH, RDP, VNC, or SFTP, which can disrupt their work if they know the session ID.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- gnmyt Nexterm
From 1.0.6-OPEN-PREVIEW · through 1.2.2-BETA
References 6
Questions about CVE-2026-120200
What does this mean?
An authenticated Nexterm user can hibernate, resume, or terminate another user's remote session, which disrupts live SSH, RDP, VNC, or SFTP sessions. The attacker needs to know or obtain that other user's session ID.Source: github.com
Am I affected, and how do I check?
Nexterm versions from 1.0.6-OPEN-PREVIEW through 1.2.2-BETA are in the affected range. To check, compare the installed Nexterm version against that range.Source: github.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target is confirmed. Check the Nexterm project for a release that addresses this issue.Source: github.com
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: cve.now feed data