TrueConf · Client · CWE-494 · published 2026-03-30
CVE-2026-3502TrueConf Client Download of Code Without Integrity Check Vulnerability
This week Known exploited in the wild.
CVE-2026-3502 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-04-02. EPSS estimates a 5.8% chance of exploitation in the next 30 days, higher than 93% of all CVEs. This Client vulnerability: CVSS 7.8 (v3.1), a successful attack gives total control of the component. CISA’s required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. US federal agencies must remediate by 2026-04-16. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (federal due date 2026-04-16)
Patch events
App server & middlewareTrueConf Client
Download of Code Without Integrity CheckCVE-2026-3502
Why: Known exploited in the wild.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2026-04-02 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 5.8% (93th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.8 (v3.1)CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-494: Download of Code Without Integrity Check
More from this vendor: all TrueConf vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- TrueConf TrueConf Client
TrueConf Client versions 8.1.0 through 8.5.2(affected)
Description (from the CVE record)#
TrueConf Client downloads application update code and applies it without performing verification. An attacker who is able to influence the update delivery path can substitute a tampered update payload. If the payload is executed or installed by the updater, this may result in arbitrary code execution in the context of the updating process or user.
Quoted from the CVE Program record.