# CVE-2026-108889: Missing authorization in Cloud Billing

> Local attackers can exploit insufficient access control in the LWBilling64.sys driver to terminate arbitrary processes, potentially causing denial of service or privilege escalation.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-wgpj-m7xc-f5q8

## What is CVE-2026-108889?

CVE-2026-108889 is a medium-severity missing authorization vulnerability in Yungengxin Cloud Billing, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw has been found in Yungengxin Cloud Billing 2024.11.28.11. Affected by this vulnerability is the function sub_14000443C in the library LWBilling64.sys of the component IOCTL Process Termination. Executing a manipulation of the argument Pid can lead to exposed ioctl with insufficient access control. The attack needs to be launched locally. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control)

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


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

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

## Is CVE-2026-108889 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108889 is a medium-severity missing authorization vulnerability in Yungengxin Cloud Billing, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108889 in the wild and no public exploit code.

Affected product: Yungengxin Cloud Billing. 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-108889/ (Markdown: https://insights.sbomify.com/CVE-2026-108889/index.md)
```

## Sources

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

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