# CVE-2025-26318: Information disclosure in TSplus Remote Access

> Remote attackers can retrieve a list of all domain accounts connected to TSplus Remote Access, exposing sensitive user information.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-jxrw-5fgg-2485

## What is CVE-2025-26318?

CVE-2025-26318 is a medium-severity vulnerability in TSplus Remote Access, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hb.exe in TSplus Remote Access before 17.30 2024-10-30 allows remote attackers to retrieve a list of all domain accounts currently connected to the application.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-26318?


## How do I fix CVE-2025-26318?

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

## Is CVE-2025-26318 being exploited?

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

Public exploit code:

- POC CVE-2025-26318 (github_poc): https://github.com/Frozenka/CVE-2025-26318

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26318 and fix it if it is affected.

What it is: CVE-2025-26318 is a medium-severity vulnerability in TSplus Remote Access, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26318 exists.

Affected product: TSplus Remote Access. 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-2025-26318/ (Markdown: https://insights.sbomify.com/CVE-2025-26318/index.md)
```

## Sources

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

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