HIGH 8.0

CVE-2026-12218: Yealink SIP-T46U Stack Buffer Overflow RCE Vulnerability

Yealink SIP-T46U IP phones running firmware version 108.87.50.1 contain a stack-based buffer overflow vulnerability in the web service. An attacker on the local network with user-level privileges can exploit this flaw by sending a specially crafted request to the `/api/inner/beforewifitest` endpoint, potentially executing arbitrary code or crashing the device. The vulnerability has been publicly disclosed, though the vendor is actively developing a patch.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.0 HIGH · CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-119, CWE-121
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-27

NVD description (verbatim)

A vulnerability was detected in Yealink SIP-T46U 108.87.50.1. The affected element is the function StartReportInformation of the file /api/inner/beforewifitest of the component Web FastCGI Service. The manipulation of the argument port results in stack-based buffer overflow. Access to the local network is required for this attack. The exploit is now public and may be used. The vendor was contacted early about this disclosure and is working on a patch to fix it.

5 reference(s) · View on NVD →

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

Technical summary

CVE-2026-12218 is a stack-based buffer overflow (CWE-119, CWE-121) in the Web FastCGI Service of Yealink SIP-T46U 108.87.50.1. The vulnerability exists in the StartReportInformation function within the `/api/inner/beforewifitest` API endpoint. Improper bounds checking on the 'port' parameter allows an authenticated local network attacker to overflow the stack, potentially leading to memory corruption, information disclosure, or code execution. The CVSS 3.1 score of 8.0 (HIGH) reflects the high impact to confidentiality, integrity, and availability, though exploitation requires network adjacency and valid user credentials.

Business impact

A compromised SIP-T46U device could serve as an entry point for lateral movement within an organization's telephony infrastructure. Attackers gaining code execution could eavesdrop on voice calls, intercept credentials, modify call routing, or use the device as a pivot to attack other networked systems. Organizations relying on Yealink phones for secure communications face both immediate confidentiality and integrity risks until patching is deployed.

Affected systems

Yealink SIP-T46U devices running firmware version 108.87.50.1 are confirmed affected. Other versions and related Yealink SIP models may be vulnerable but have not been explicitly confirmed in available advisories. Organizations should audit their current firmware versions and cross-reference against Yealink's official security bulletins to identify all affected models and versions in their environment.

Exploitability

While the vulnerability requires local network access and valid user credentials, the public disclosure and active development status mean proof-of-concept code may be available or become available soon. The relative simplicity of buffer overflow exploitation and the ease of crafting malicious web requests lowers the technical bar for exploitation. Organizations with permissive internal network policies or shared WiFi/LAN environments face elevated risk.

Remediation

Contact Yealink support and monitor their security advisories for official firmware patches. Verify the exact firmware versions deployed across your SIP-T46U fleet immediately. Until patches are available, mitigate by restricting network access to the Web FastCGI Service, limiting local network access to trusted users and devices, and disabling the `/api/inner/beforewifitest` endpoint if not operationally required. Implement network segmentation to isolate telephony devices from general office networks where possible.

Patch guidance

Yealink is developing a patch and has been engaged early in the disclosure process. Check Yealink's official security advisory page and your device management portal for firmware updates. When patches become available, verify the firmware version number against Yealink's release notes before deployment. Test patches in a staging environment with a representative SIP-T46U device to confirm call handling and feature functionality remain intact. Coordinate patching with your phone provisioning system to ensure automated rollout does not disrupt service.

Detection guidance

Monitor for HTTP POST/GET requests to `/api/inner/beforewifitest` with suspicious or oversized 'port' parameter values. Look for unusual process behavior on SIP-T46U devices following API calls (e.g., core dumps, unexpected restarts, or new processes spawning). Correlate device syslog entries with any observed network reconnaissance activity on your telephony segment. Organizations with access to device-level packet capture should inspect for requests containing buffer overflow payloads targeting the StartReportInformation function.

Why prioritize this

This vulnerability merits urgent attention because it combines high CVSS impact (confidentiality, integrity, availability all affected), public exploit availability, active vendor patching, and direct access to voice communications. Although it requires local network access and user authentication, the ubiquity of Yealink SIP phones in enterprise environments and the sensitive nature of telephony data elevate business risk substantially. Exploit availability accelerates the timeline for remediation.

Risk score, explained

The CVSS 3.1 score of 8.0 reflects the high severity: the vulnerability allows remote code execution or denial of service on a sensitive communications device with high confidentiality and integrity impact. The score is tempered by the requirement for adjacent network access (AV:A) and low-privilege user authentication (PR:L), which are typical controls in managed office environments but not absolute barriers in organizations with guest networks or contractor access.

Frequently asked questions

Does this vulnerability affect all Yealink SIP phone models?

Currently, only the SIP-T46U running firmware 108.87.50.1 is confirmed vulnerable. However, it is prudent to check Yealink's official security advisory to determine whether other SIP-T4x series models or earlier/later firmware versions are affected. Contact Yealink support with your specific deployment details.

Can this vulnerability be exploited over the internet?

No. The vulnerability requires local network adjacency (AV:A in the CVSS vector), meaning the attacker must be on the same subnet or LAN as the affected device. Internet-facing SIP-T46U devices are not directly exploitable from the public internet, but an attacker on the corporate WiFi or LAN can exploit it.

What should we do if we do not have a patch yet?

Until a patch is released, implement network-level mitigations: restrict access to the Web FastCGI Service port (typically 8025) using firewall rules, limit SSH and web admin access to trusted administrative users, and physically isolate the telephony LAN from general office networks if feasible. Monitor Yealink's security page weekly for patch releases and prepare a patching plan in advance.

Is this vulnerability listed on CISA's Known Exploited Vulnerabilities catalog?

No, as of the current publication date, this vulnerability is not on the CISA KEV catalog. However, public exploit code is available, which increases the likelihood of being added if active exploitation is observed in the wild. Organizations should not rely on KEV listing as their sole trigger for remediation.

This analysis is based on the CVE record published on 2026-06-15 and modified on 2026-06-27. Information is subject to change as the vendor releases patches and additional advisory details. Organizations must verify patch availability directly from Yealink's official security advisories before deploying any updates. SEC.co does not provide exploit code and does not endorse or provide instructions for weaponizing vulnerabilities. This intelligence is provided for defensive security purposes only. Always test patches in a non-production environment and follow your organization's change management and testing procedures. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).