TrueConf Client
CVE-2026-3502
TrueConf Client contains a download of code without integrity check vulnerability. 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.
What this means for your business
- It affects TrueConf Client. It matters if your company, or a supplier that handles your data, runs it.
- Attackers are already using it. CISA added it to its list of flaws used in real attacks on 2 April 2026.
- FIRST's prediction model gives it a 6% chance of attack attempts being seen in the next 30 days, ranking above 92% of all known flaws.
What to do
- 1Check whether your company or your suppliers run TrueConf Client.
- 2If you do, follow CISA's required action below. No patch reference has been published yet.
- 3Treat it as urgent. US federal agencies must fix it by 16 April 2026. That deadline does not apply to private companies, but it shows how seriously CISA takes it.
- 4Because attackers have used it, check the affected systems for signs of a break-in, not only for the update.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
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’s wording, unedited.
Scoring
- CVSS
- Not yet scored
Dates
- Published
- 2026-04-02
- Added to KEV
- 2026-04-02
- Remediation due
- 2026-04-16
- Sources
- CISA KEV