# CVE-2026-76943: Xiiaozet LK100W Authentication Bypass Using an Alternate Path or Channel

> Attackers can bypass authentication on the Xiiaozet LK100W administrative service to execute commands and compromise the device.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-6x82-vfrh-gxpc

## What is CVE-2026-76943?

CVE-2026-76943 is a critical authentication bypass vulnerability in Xiiaozet LK100W, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Xiiaozet LK100Wt contains an authentication weakness within an 
administrative service that may allow an attacker to bypass intended 
access controls and obtain command execution capabilities. Successful 
exploitation could allow unauthorized interaction with privileged 
functionality and may lead to complete device compromise.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-76943 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76943 is a critical authentication bypass vulnerability in Xiiaozet LK100W, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76943 in the wild and no public exploit code.

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

## Sources

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

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