MEDIUM 6.3

CVE-2026-12219: Yealink SIP-T46U Command Injection in Firmware 108.86.0.118

Yealink SIP-T46U phone systems running firmware version 108.86.0.118 contain a command injection vulnerability in their web-based diagnostic interface. An authenticated user can exploit this flaw by manipulating a time parameter to execute arbitrary system commands on the affected device. The vulnerability has been disclosed publicly, meaning attackers have knowledge of how to exploit it. Upgrading to firmware version 108.87.0.23 eliminates the risk.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-74, CWE-77
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-27

NVD description (verbatim)

A flaw has been found in Yealink SIP-T46U 108.86.0.118. The impacted element is the function mod_diagnose.CommandShellByType of the file /api/diagnosis/start of the component Web FastCGI Service. This manipulation of the argument Time causes command injection. The attack can be initiated remotely. The exploit has been published and may be used. Upgrading to version 108.87.0.23 is sufficient to resolve this issue. It is advisable to upgrade the affected component.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability exists in the mod_diagnose.CommandShellByType function within the Web FastCGI Service component, specifically in the /api/diagnosis/start endpoint. The flaw arises from insufficient input validation on the Time argument, allowing command injection attacks. The weakness is classified under CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) and CWE-77 (Improper Neutralization of Special Elements used in a Command). Exploitation requires valid credentials (CVSS reflects PR:L—Low privilege requirement), and no user interaction is needed once authenticated. Network accessibility and lack of complexity protections make this a straightforward attack vector.

Business impact

Compromised Yealink phones can be leveraged as beachheads into corporate voice infrastructure and the broader network. An attacker with valid credentials (a compromised user account, vendor support access, or default credentials if not changed) gains the ability to execute commands with the privileges of the Web FastCGI Service process. This could lead to unauthorized access to call logs, configuration data, or lateral movement to connected systems. For organizations relying on Yealink devices for unified communications, this represents a post-authentication privilege escalation risk that could disrupt or compromise voice operations.

Affected systems

Yealink SIP-T46U IP phones running firmware version 108.86.0.118 are confirmed vulnerable. Organizations should inventory their Yealink device fleet and check current firmware versions. The SIP-T46U is a mid-to-enterprise-range handset commonly deployed in larger organizations; scope and impact depend on deployment breadth and credential hygiene in your environment.

Exploitability

The vulnerability requires valid authentication to the device's web interface—an attacker cannot exploit it anonymously. However, the CVSS score of 6.3 (Medium) reflects the practical reality that compromised credentials, default accounts, or insider threats can make this exploitable in real-world scenarios. The fact that exploit details have been published increases the likelihood of opportunistic or targeted attacks against known vulnerable instances. The attack requires no special techniques or complex setup once authentication is obtained.

Remediation

Upgrade affected Yealink SIP-T46U devices to firmware version 108.87.0.23 or later. Before patching, enforce strong, unique passwords on all Yealink device web interfaces and disable remote management if not operationally necessary. Restrict network access to the /api/diagnosis/start endpoint using firewall rules or IP allowlisting. Monitor authentication logs for suspicious login attempts on these devices.

Patch guidance

Yealink provides firmware updates via their vendor portal or through push mechanisms if auto-update is enabled. Verify the exact firmware version on affected devices by accessing the device web interface (typically http://<device-ip>) and navigating to Settings > Firmware. Download firmware 108.87.0.23 from Yealink's support site and follow their standard firmware upgrade procedures. Test the update in a non-critical device or lab environment first. After upgrade, verify devices have rebooted and are operating normally before rolling out to production.

Detection guidance

Monitor for POST requests to /api/diagnosis/start endpoints on your Yealink devices. Look for unusual or repeated authentication failures on device web interfaces, particularly if they precede successful logins. Check Web FastCGI Service logs (if accessible) for errors or command execution patterns. Use network segmentation to isolate phone system traffic and apply IDS/IPS rules to alert on suspicious parameter values in /api/diagnosis/ requests. Track firmware versions across your fleet using device management tools or periodic audits.

Why prioritize this

This vulnerability merits prompt but measured attention. It requires authentication, lowering immediate risk for properly secured deployments. However, the combination of public exploit availability, remote exploitability, and potential for lateral movement into voice and network infrastructure justifies prioritization above routine patches. Organizations with weak phone system password policies or those who have not changed vendor default credentials should treat this as higher priority.

Risk score, explained

The CVSS 3.1 score of 6.3 (Medium) reflects a remote network attack (AV:N) with low complexity (AC:L), low privilege requirement (PR:L), and no user interaction needed (UI:N). The impact is limited to the affected system (S:U) but includes confidentiality, integrity, and availability concerns (C:L/I:L/A:L). The score does not account for the published exploit status or organizational context; your internal risk may be higher or lower depending on credential management, network segmentation, and device exposure.

Frequently asked questions

Can this vulnerability be exploited without valid credentials?

No. The CVSS vector PR:L indicates a low-privilege authenticated user is required. An attacker must have valid credentials to access the device's web diagnostic interface. However, this means compromised user accounts, shared vendor credentials, or unchanged default passwords pose real risk.

What happens if we do not upgrade immediately?

If your devices are isolated from the internet and access is restricted to trusted internal users, immediate risk is lower. However, given the published exploit status, you should prioritize patching within 30 days. If your phones are exposed to untrusted networks or you cannot guarantee strong credential management, upgrade sooner.

Does this affect only the SIP-T46U model?

The vulnerability is confirmed on the SIP-T46U running firmware 108.86.0.118. Other Yealink models may share the same vulnerable firmware branch—consult Yealink's security advisory to determine the full scope of affected products and compatible upgrade paths.

How do we prevent exploitation while patching is in progress?

Enforce complex, unique passwords on all device web interfaces; disable remote management and web access if not operationally required; restrict network access to the /api/diagnosis/start endpoint using firewall rules; and monitor authentication logs for suspicious activity. These controls reduce the likelihood of successful exploitation even if a device remains unpatched temporarily.

This analysis is based on published CVE data and vendor advisories as of 2026-06-27. Organizations should verify firmware versions, compatibility, and patch applicability against Yealink's official documentation before deploying updates. This explainer provides contextual guidance and does not constitute professional security advice; consult your security team or a qualified vendor partner for deployment decisions specific to your environment. No exploit code or weaponized proof-of-concept is provided or endorsed. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).