Quick answers
- Is CVE-2026-7208 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7208 being exploited in the wild.
- How severe is CVE-2026-7208?
- Medium severity, with a CVSS score of 5.3, published 14 September 2026.
- Which products and versions are affected?
- Yealink SIP-T33G 124.86.x.x prior to 124.87.0.0.
- Is there a fix for CVE-2026-7208?
- A patch was published on 2026-09-14: Fix available in firmware version 124.87.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-7208 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-7208?
- Check whether you run Yealink SIP-T33G at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a race condition (CWE-362) in the firmware's diagnostic module where output files are written to predictable paths. An authenticated attacker can exploit a window of time between when a diagnostic process (e.g., traceroute, ping) is initiated and when it completes, by simultaneously invoking a file deletion endpoint to remove the temporary output files. The predictable file paths and lack of proper synchronization allow the attacker to reliably interrupt the process and leave the system in an inconsistent state. The attack requires authentication and is triggered via network access. Firmware versions 124.86.x.x prior to 124.87.0.0 are affected; upgrading to 124.87.0.0 or later resolves the issue.
Affected products
- Yealink SIP-T33G 124.86.x.x prior to 124.87.0.0
Timeline
- 2026-09-14: disclosed
- 2026-09-14: patched: Fix available in firmware version 124.87.0.0