Skip to main content
Mallory
High

Stack-based Buffer Overflow in Yealink SIP-T46U Firmware Chunk Upload Handler

IdentifiersCVE-2026-12221CWE-121· Stack-based Buffer Overflow

CVE-2026-12221 is a stack-based buffer overflow vulnerability affecting Yealink SIP-T46U firmware version 108.86.0.118. The flaw is in the Firmware Chunk Upload Handler exposed via /api/upgrade/upgrade, specifically involving the use of sprintf. According to the provided content, manipulation of the uid/start_offset argument can cause a stack-based buffer overflow. The issue is reachable over the adjacent/local network and a public exploit has been reported. Successful exploitation could allow memory corruption during firmware chunk upload processing.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in severe compromise of the affected device, consistent with arbitrary memory corruption from a stack-based buffer overflow. Based on the provided CVSS assessments, the expected impact includes high confidentiality, integrity, and availability impact. In practical terms, exploitation may enable code execution in the context of the vulnerable service, device takeover, denial of service, or other undefined behavior depending on exploit reliability and runtime protections.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the affected device's management and upgrade interfaces, especially /api/upgrade/upgrade, to trusted administrative hosts only. Prevent exposure of the interface beyond the required management network, segment voice infrastructure from untrusted internal networks, and apply ACLs or firewall rules to limit adjacent-network reachability. Disable or tightly control firmware upgrade functionality where operationally feasible, and monitor for suspicious requests targeting firmware chunk upload parameters such as uid and start_offset. Given that a public exploit reportedly exists, prioritize compensating controls until a vendor fix is available.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed firmware release if and when Yealink publishes one for SIP-T46U. Because the provided content identifies the affected version as 108.86.0.118 but does not specify a patched version, the exact fixed release is currently not available. If no patch is available, engage the vendor for an official remediation path and track subsequent advisories.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity12

Community discussion across Reddit, Mastodon, and other social sources.