CVE-2026-122118 In certain Yealink products before 2026-04-15, when the Wi-Fi AP function is enabled, a default 8-digit numeric PSK with insufficient strength is used.
High 7.4
Published
Updated
Check this codebase for CVE-2026-122118 and fix it if it is affected.
What it is: CVE-2026-122118 is a high-severity vulnerability in Yealink AVHub, published on 4 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-122118 in the wild and no public exploit code.
Affected product: Yealink AVHub. 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-122118/ (Markdown: https://insights.sbomify.com/CVE-2026-122118/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-122118?
CVE-2026-122118 is a high-severity vulnerability in Yealink AVHub, published on 4 Nov 2026.
Official description
In certain Yealink products before 2026-04-15, when the Wi-Fi AP function is enabled, a default 8-digit numeric PSK with insufficient strength is used. Attackers can exploit this weakness via brute-force attacks to gain unauthorized network access and intercept Wi-Fi traffic.
Weakness: CWE-334
Which versions are affected by CVE-2026-122118?
How do I fix CVE-2026-122118?
No fix has been published for CVE-2026-122118 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-122118 being exploited?
There is no known exploitation of CVE-2026-122118 in the wild and no public exploit code.
Sources
Also known as GHSA-763v-w5mm-jf4f.