# CVE-2026-111617: WHartTest through 2.8.1 Missing Authentication on UI-Automation WebSocket Endpoints

> Unauthenticated attackers can access WebSocket endpoints to intercept test payloads and spoof results in WHartTest.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-6gwv-fx4p-w9x8

## What is CVE-2026-111617?

CVE-2026-111617 is a medium-severity missing authorization vulnerability in MGdaasLab WHartTest, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WHartTest through 2.8.1 contains a missing authentication vulnerability that allows unauthenticated attackers to connect to the /ws/ui/web/ and /ws/ui/actuator/ WebSocket endpoints because UiAutomationConsumer accepts every connection. Attackers can register an actuator with a client-supplied id to intercept other users' test-case payloads, receive broadcast step results, and spoof results and screen frames into victim sessions.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-111617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111617 is a medium-severity missing authorization vulnerability in MGdaasLab WHartTest, published on 16 Oct 2026. 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-2026-111617 exists.

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

## Sources

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

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