# CVE-2026-6947: D-Link｜DWM-222W USB Wi-Fi Adapter - Brute-Force Protection Bypass

> Attackers can bypass login attempt limits on D-Link DWM-222W adapters to perform brute-force attacks and gain device control.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/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:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-j7j4-xj8f-m78g

## What is CVE-2026-6947?

CVE-2026-6947 is a high-severity vulnerability in D-Link DWM-222W, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DWM-222W USB Wi-Fi Adapter developed by D-Link has a Brute-Force Protection Bypass vulnerability, allowing unauthenticated adjacent network attackers to bypass login attempt limits to perform brute-force attacks to gain control over the device.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-6947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6947 is a high-severity vulnerability in D-Link DWM-222W, published on 24 Apr 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-6947 in the wild and no public exploit code.

Affected product: D-Link DWM-222W. 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-6947/ (Markdown: https://insights.sbomify.com/CVE-2026-6947/index.md)
```

## Sources

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

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