CVE-2026-122116VulnerabilityPublished 4 Nov 2026

Certain Yealink terminal devices before 2026-04-21 contain an improper access control vulnerability in the Wi-Fi

Source GCVE Database

Compare

Authoritative record:CVE-2026-122116· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 124.87.0.22 when convenient.

Data as of 4 Nov 2026, 19:45 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (mitre)	CVSS 3.1	4.3

Patch: Available – fixed in 124.87.0.22, 108.87.0.23, 96.87.0.24 +9

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9q83-h82m-rw63

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
YealinkT3XW Series Phones	Affected >=124.85.0.1 <124.87.0.22	Fixed in 124.87.0.22
YealinkT4X Series Phones	Affected >=108.85.0.1 <108.87.0.23	Fixed in 108.87.0.23
YealinkT5X Series Phones	Affected >=96.85.0.1 <96.87.0.24	Fixed in 96.87.0.24
YealinkT7X Series Phones	Affected >=185.87.0.5 <185.87.0.39	Fixed in 185.87.0.39
YealinkSIP-T85W、SIP-T87W	Affected >=185.87.0.5 <185.87.0.39	Fixed in 185.87.0.39
YealinkAX83H、AX86R	Affected >=180.86.0.1 <180.87.0.15	Fixed in 180.87.0.15

AI-suggested

Apply the latest Yealink firmware released on or after 2026-04-21, which restricts 802.1X configuration modification privileges to administrator accounts only by default. This official fix addresses the improper access control vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

Certain Yealink terminal devices released before April 21, 2026, have an improper access control vulnerability in the Wi-Fi 802.1X PEAP network configuration function. This vulnerability allows unauthorized users to access 802.1X network authentication credentials. Yealink has addressed this issue in the latest firmware by restricting modification privileges of the 802.1X configuration to administrator accounts only by default.

Impact

The vulnerability exposes 802.1X network access authentication credentials to unauthorized users, potentially allowing them to gain unauthorized network access or disrupt network security. The CVSS v3.1 base score is 4.3 (medium severity), indicating a network attack vector with low complexity and requiring low privileges but no user interaction, resulting in a low impact on availability and no impact on confidentiality or integrity.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 19:45 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats