Stack-based buffer overflow in Yealink SIP-T46U Web FastCGI Service

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-12218?

CVE-2026-12218 is a vulnerability classified as Stack-based Buffer Overflow and Improper Restriction of Operations within the Bounds of a Memory Buffer, affecting SIP-T46U (affected versions: 108.87.50.1). This vulnerability is rated High, with a CVSS score of 8.6. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

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.

Affected products and scope

  • Affected product: Yealink SIP-T46U.
  • Confirmed affected version: 108.87.50.1.
  • The relevant component is Web FastCGI Service, including /api/inner/beforewifitest and the StartReportInformation function.
  • No fixed version has been confirmed. The status of other firmware branches cannot be inferred from this record and requires confirmation from Yealink.

Technical details

The flaw is in the Web FastCGI Service component, in the StartReportInformation function associated with /api/inner/beforewifitest. Processing attacker-controlled data in the port argument can cause a stack-based buffer overflow, classified as CWE-121 and related to CWE-119. The supplied evidence indicates that exploitation requires access from a local or adjacent network, low privileges, and no user interaction. The buffer size, bounds-checking condition, minimum triggering input, and ability to control execution flow are not documented. Arbitrary code execution therefore remains a possible consequence of the memory corruption, not a confirmed result of the available evidence.

Exploitability

  • The vulnerable service is reachable from a local or adjacent network, not through direct physical access.
  • The supplied scoring facts indicate that low privileges are required, no user interaction is needed, and attack complexity is low.
  • A public proof of concept is reported to exist, and technical details have been disclosed.
  • The available evidence does not establish exploitation in the wild or identify a specific campaign. The exact request format, authentication mechanism, and complete exploit chain are also not documented.

Technical impact

The flaw corrupts stack memory in the Web FastCGI Service process. The immediate technical outcome could be a crash or denial of service; under suitable conditions, memory corruption could permit state modification or code execution, but the available evidence does not confirm control of execution. The expected impact is within the affected device scope because the supplied assessment records unchanged scope. Organisational consequences could include unavailable phones, altered device or service state, and possible compromise of information handled by the device. The low-privilege requirement and local or adjacent network reachability reduce exposure compared with an unauthenticated Internet-facing flaw, but they do not remove the risk in broadly accessible or poorly segmented internal networks.

Business impact

The flaw could cause affected phones to crash or stop providing voice services, disrupting communications and business operations. If successfully exploited, the memory corruption could create a risk of data disclosure, state changes, or disruption of services handled by the device. These are technically possible consequences of the vulnerability and its recorded impact, not evidence of a specific breach or data leak. Organizations should prioritize phones located in network segments shared with untrusted users or devices.

Remediation

  1. Verify all Yealink SIP-T46U devices running 108.87.50.1 and place them in the remediation queue.
  2. Monitor Yealink security updates and apply the official patch as soon as it is released. No exact fixed release is confirmed at this time.
  3. Until a patch is available, restrict unnecessary access to the devices from adjacent or untrusted network segments and allow management access only from trusted sources. This is a precautionary risk-reduction measure, not a vendor-confirmed workaround.
  4. If the affected devices cannot be patched or their exposure cannot be controlled, consider replacing them, consistent with the alternative-product guidance recorded by the CNA source.

Detection

  1. Inventory Yealink SIP-T46U devices and verify the firmware versions in use, prioritizing devices on the affected release.
  2. Identify devices that expose or can receive traffic to Web FastCGI Service and /api/inner/beforewifitest from adjacent network segments.
  3. Review web service or FastCGI access logs, where available, for requests to the path and unusual port values. This is a precautionary search, not a vendor-confirmed indicator of compromise.
  4. Check system logs, watchdog events, unexpected restarts, and crashes after requests involving the affected component.
  5. Do not run the public proof of concept against production phones. The absence of related log entries does not prove that a device is safe.
Sources (17)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.