CVE-2026-12223: Yealink SIP-T46U Command Injection Vulnerability in Web Service
Yealink SIP-T46U IP phones running firmware version 108.86.0.118 contain a command injection vulnerability in their web service that allows authenticated users on the local network to execute arbitrary commands by manipulating network parameters. An attacker with local network access and valid credentials can exploit this flaw to compromise the phone's integrity and confidentiality. A patched firmware version (108.87.0.23) is available, though the vendor notes the fix currently exists only in a technical support branch and has not been publicly released yet.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.5 MEDIUM · CVSS:3.1/AV:A/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 vulnerability was identified in Yealink SIP-T46U 108.86.0.118. Affected by this vulnerability is the function mod_webd.TFTPUploadIperf of the file /api/inner/tftpuploadiperf of the component Web FastCGI Service. The manipulation of the argument ip/port leads to command injection. The attack needs to be initiated within the local network. The exploit is publicly available and might be used. Upgrading to version 108.87.0.23 addresses this issue. Upgrading the affected component is recommended. The vendor explains: "It has been fixed (...) for our technical support branch. However, please note that this specific support branch firmware is not publicly released yet."
5 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the mod_webd.TFTPUploadIperf function within the Web FastCGI Service component. It processes the /api/inner/tftpuploadiperf endpoint and fails to properly sanitize the ip and port parameters, allowing an attacker to inject shell commands that are then executed by the web service process. The flaw is classified under CWE-74 (Improper Neutralization of Special Elements in Output) and CWE-77 (Improper Neutralization of Special Elements used in a Command). The attack vector requires local network proximity and valid authentication credentials, limiting exposure to internal-only threats.
Business impact
Compromise of Yealink phones in enterprise environments could expose sensitive voice communications, allow unauthorized use of the device for lateral network reconnaissance, or disrupt VoIP service availability. Because these phones often sit on converged networks with corporate data systems, a compromised endpoint could serve as a pivot point for further attacks. However, the requirement for local network access and authentication credentials substantially constrains the blast radius compared to remote-unauthenticated vulnerabilities.
Affected systems
Yealink SIP-T46U devices running firmware version 108.86.0.118 are confirmed vulnerable. Organizations should inventory their Yealink phone deployments and identify which models and firmware versions are in use, particularly any SIP-T46U units. The vendor's firmware version listing should be checked to determine the precise scope in your environment.
Exploitability
Exploitation requires an attacker with both local network access and valid user credentials on the device or its authentication domain. While a public exploit exists, the prerequisite authentication barrier significantly limits opportunistic exploitation. This is not an easy remote unauthenticated attack; it represents a local insider risk or a risk from an attacker who has already compromised network access.
Remediation
Upgrade Yealink SIP-T46U devices to firmware version 108.87.0.23 or later. The vendor has confirmed the fix is available in their technical support branch; verify the availability and release status of this firmware through your Yealink support channel or account team before deployment. Organizations unable to upgrade immediately should restrict administrative access to the devices and limit local network exposure to trusted personnel only.
Patch guidance
Contact your Yealink technical support representative to obtain firmware version 108.87.0.23. Because the vendor notes this version currently exists only in a technical support branch and is not yet publicly released, coordinate with Yealink's support organization to confirm availability and obtain signed, validated firmware images. Test patches in a lab environment with representative Yealink models before wide deployment. Plan patching during low-traffic periods to minimize voice service disruption.
Detection guidance
Monitor access logs to the /api/inner/tftpuploadiperf endpoint on Yealink devices, particularly requests containing unusual or shell-like syntax in the ip or port parameters (e.g., backticks, semicolons, pipes, or command substitution characters). Inspect HTTP POST/GET requests for payloads attempting command injection. Segment Yealink phones on a dedicated VLAN if possible to reduce lateral movement risk and simplify logging. Ensure adequate logging of administrative and API-level access to these devices.
Why prioritize this
This vulnerability scores MEDIUM (CVSS 5.5) due to the requirement for local network presence and authentication. It does not appear on the CISA KEV catalog, indicating it is not currently being actively exploited at scale in the wild. However, the existence of public exploit code and the presence of vulnerable phones in many enterprises warrant timely patching. Prioritize this alongside other network device updates, particularly if your organization has a large Yealink footprint or if the affected devices are located in high-security network zones.
Risk score, explained
The CVSS 3.1 score of 5.5 (MEDIUM) reflects a relatively constrained attack scenario: local network requirement (AV:A), low complexity (AC:L), low privilege requirement (PR:L), no user interaction (UI:N), unchanged scope (S:U), and limited impact to confidentiality, integrity, and availability (C:L/I:L/A:L). Each impact category is rated Low rather than High, because command injection on a single phone endpoint does not typically compromise entire systems. The local and authenticated nature of the attack substantially reduces the score compared to what a remote unauthenticated command injection would receive.
Frequently asked questions
Do we need to patch immediately if we only use Yealink phones internally with restricted network access?
Patching should still be scheduled promptly, but you may deprioritize relative to public-facing or less-protected systems. Verify your Yealink firmware versions and access controls. If phones are isolated on a dedicated VLAN with strong authentication and limited administrative access, you can plan patches during a normal maintenance window. Do not delay indefinitely, especially if the firmware becomes publicly available.
Is this vulnerability exploitable remotely over the internet?
No. The vulnerability requires local network access. It cannot be exploited by an attacker on the public internet. This significantly reduces risk for organizations with proper network segmentation and firewall controls.
The vendor says the patch is not publicly released. How do we obtain it?
Contact Yealink technical support directly through your account team or support portal. Provide them with your device serial numbers, current firmware version, and request the availability of firmware 108.87.0.23. Yealink typically releases patches through their support channels before or alongside public announcements. Ensure you obtain firmware from official Yealink sources and verify signatures before deployment.
What if we cannot upgrade immediately?
Mitigate by restricting local network access to Yealink devices to trusted personnel only, disabling unnecessary remote management features, and enforcing strong authentication. Implement network segmentation (VLANs) to isolate phones from sensitive systems. Monitor administrative access logs and API requests to these devices. Set a firm patching deadline and track progress toward remediation.
This analysis is based on information published as of the modification date (2026-06-27). Patch availability, vendor guidance, and threat intelligence may change. Verify all patch versions and availability directly with Yealink before deployment. This vulnerability assessment does not constitute a substitute for your organization's own vulnerability management and risk assessment processes. Test patches in a controlled environment before production use. SEC.co provides this analysis for informational purposes and accepts no liability for decisions made based on this content. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10060MEDIUMTRENDnet TEW-432BRP Command Injection—End-of-Life Router Vulnerability
- CVE-2026-10061MEDIUMTRENDnet TEW-432BRP Command Injection Vulnerability – Remediation via Replacement
- CVE-2026-10127MEDIUMEdimax BR-6478AC Command Injection in Firmware 1.23
- CVE-2026-10166MEDIUMEdimax BR-6478AC Command Injection – Authentication Required
- CVE-2026-10180MEDIUMTRENDnet TEW-432BRP Command Injection Vulnerability – Hardware Retirement Required
- CVE-2026-10182MEDIUMTRENDnet TEW-432BRP Command Injection – Unpatched EOL Device
- CVE-2026-10550MEDIUMCommand Injection in elunez eladmin Deployment Module
- CVE-2026-10878MEDIUMD-Link DWR-M920 Command Injection Vulnerability – Patch Now