# CVE-2026-8232: Dotouch XproUPF UPF Process libvlib.so vlib_worker_loop denial of service

> An attacker with permissions can cause a denial of service in the Dotouch XproUPF User Plane Function via the vlib_worker_loop function.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-637x-347r-m83j

## What is CVE-2026-8232?

CVE-2026-8232 is a medium-severity denial of service vulnerability in Dotouch XproUPF, published on 10 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Dotouch XproUPF 2.0.0-release-088aa7c4. This impacts the function vlib_worker_loop in the library /usr/xpro/upf/tools/libs/libvlib.so of the component UPF Process. The manipulation results in denial of service. The vendor was contacted early about this disclosure.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-8232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8232 is a medium-severity denial of service vulnerability in Dotouch XproUPF, published on 10 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8232 exists.

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

## Sources

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

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