CVE-2026-3502
CVE-2026-3502 is a high-severity vulnerability (CVSS 3.1 base score 7.8). TrueConf Client contains a download of code without integrity check vulnerability. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-04-02, with a remediation due date of 2026-04-16 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 5.8% probability of exploitation in the next 30 days, in the 93rd percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.8 HIGH
- EPSS
- 5.8% (93rd pct)
- CISA KEV
- Exploited
- Published
- 2026-03-30
- Weakness
- CWE-494
TrueConf Client Download of Code Without Integrity Check Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
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.
CISA notes
https://trueconf.com/blog/update/trueconf-8-5 ; https://trueconf.com/downloads/windows.html ; https://nvd.nist.gov/vuln/detail/CVE-2026-3502
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2026-3502 to the KEV catalog 3 days after its CVE record was published. The median for entries added in 2026 so far is 12.5 days.
- It is one of 3 TrueConf entries in the CISA KEV catalog, and one of 3 added in 2026.
- Its current EPSS score (5.8%) is higher than that of 18% of CISA KEV entries.
Severity
CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:LOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2026-03-31).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| TrueConf | TrueConf TrueConf Client | TrueConf Client versions 8.1.0 through 8.5.2 |
References
1 linksOther references
Record Details
- Published
- 2026-03-30
- Last updated
- 2026-04-03
- Assigner (CNA)
- checkpoint
- Credited to
- -
More from TrueConf
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.