Yealink SIP-T33G firmware versions 124.86.x.x prior to 124.87.0.0 contain a race condition vulnerability that allows authenticated attackers to interrupt active diagnostic processes by concurrently deleting output files written to predictable paths under the diagnostic directory. Attackers can trigger a diagnostic operation such as traceroute or ping and simultaneously invoke the file deletion endpoint to terminate the running process, leaving the system in an inconsistent state.
CVE-2026-7208
Score 5.3 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 14, 2026
Last Modified
September 14, 2026
Advisory Details (3)
Auto-updated Sep 14, 2026Yealink SIP-T33G < 124.87.0.0 Race Condition via Diagnostic File Deletion | Advisories | VulnCheck
https://www.vulncheck.com/advisories/yealink-sip-t33g-race-condition-via-diagnostic-file-deletionSIP-T33G - Classic Business IP Phone | Yealink
https://www.yealink.com/en/product-detail/ip-phone-t33gRace Condition on Runtime Diagnostic Files in Yealink SIP‑T33G
https://www.yealink.com/en/trust-center/security-bulletins/race-condition-on-runtime-diagnostic-files-in-yealink-sipt33gVendor Advisories for CVE-2026-7208(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 21:48 UTCEG score recompute
- 2026-09-20 21:48 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 21:31 UTCEG score recompute
- 2026-09-19 21:31 UTCGHSA enrichment
- 2026-09-18 21:15 UTCEG score recompute
- 2026-09-18 21:15 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:15 UTCEG score recompute
- 2026-09-17 20:15 UTCGHSA enrichment
- 2026-09-16 19:59 UTCEG score recompute
- 2026-09-16 19:59 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 19:41 UTCGHSA enrichment
- 2026-09-14 19:19 UTCEG score recompute
- 2026-09-14 19:19 UTCGHSA enrichment
- 2026-09-14 18:26 UTCEG score recompute
- 2026-09-14 18:25 UTCGHSA enrichment
- 2026-09-14 14:30 UTCEG score recompute
- 2026-09-14 13:30 UTCEG score recompute
- 2026-09-14 13:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-7208?
When was CVE-2026-7208 disclosed?
Is CVE-2026-7208 actively exploited?
What is the CVSS score of CVE-2026-7208?
How do I remediate CVE-2026-7208?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-7208
Is Your Infrastructure Affected by CVE-2026-7208?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.