CVE-2026-12219
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA command injection vulnerability exists in Yealink SIP-T46U phones running firmware version 108.86.0.118. The flaw is in the Web FastCGI Service's /api/diagnosis/start endpoint, specifically the mod_diagnose.CommandShellByType function. The 'Time' argument is not properly sanitized, allowing remote attackers to inject and execute arbitrary shell commands on the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the phone's web管理界面 or check the device label/boot screen to confirm the model is Yealink SIP-T46UAffected if The device is not a Yealink SIP-T46U model
-
Check the firmware versionNavigate to the phone's web interface (Status > Device Information) or dial *#*#OPTIONS#*#* on the device to access the status menu and locate the firmware version fieldAffected if The installed firmware version is below 108.87.0.23 (vulnerable versions include 108.86.0.118 and earlier)
-
Verify the web service is enabledConfirm that the Web FastCGI Service is enabled on the device (typically found in Network > Web Server settings in the phone's web management interface)Affected if The web management interface is disabled, the attack surface is reduced but the phone may still be vulnerable if the service can be re-enabled remotely
A user is affected if they have a Yealink SIP-T46U phone running firmware version below 108.87.0.23 with the web management interface accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade the Yealink SIP-T46U firmware from version 108.86.0.118 to version 108.87.0.23 or later to remediate this command injection vulnerability.
108.87.0.23
- 1. Identify Yealink SIP-T46U devices on the network running firmware version 108.86.0.118
- 2. Access the device web interface or Yealink device management system
- 3. Navigate to the firmware upgrade section
- 4. Download the fixed firmware version 108.87.0.23 from the official Yealink support portal (support.yealink.com)
- 5. Upload the firmware file to the affected device
- 6. Apply the firmware upgrade and wait for the device to reboot
- 7. Verify the device is running version 108.87.0.23 and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data