# CVE-2026-122124: On Yealink UVC40 E2 devices before 319.410.0.71, an attacker with short-term physical access can steal Wi‑Fi credentials via the USB interface.


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-rfxg-v2hf-hwcq

## What is CVE-2026-122124?

CVE-2026-122124 is a medium-severity vulnerability in Yealink UVC40 E2, published on 4 Nov 2026. 

### Official description

On Yealink UVC40 E2 devices before 319.410.0.71, an attacker with short-term physical access can steal Wi‑Fi credentials via the USB interface. Sensitive data within the firmware configuration can be abused to gain root privileges on the device. Within Wi‑Fi coverage, the attacker may perform audio and video eavesdropping with no LED alert from the device.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

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

## Is CVE-2026-122124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122124 is a medium-severity vulnerability in Yealink UVC40 E2, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122124 in the wild and no public exploit code.

Affected product: Yealink UVC40 E2. 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-122124/ (Markdown: https://insights.sbomify.com/CVE-2026-122124/index.md)
```

## Sources

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

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