CVE-2026-3502TrueConf Client Download of Code Without Integrity Check Vulnerability
CVE-2026-3502 is a download without integrity check in TrueConf Client, rated high (7.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
Code or updates are downloaded and run without checking they are genuine.
How it is reached
An attacker can exploit it from the same local network segment, with an administrator account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker run their code inside your build or your running service. The damage can spread past the vulnerable component into others.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2026-04-02: it is being exploited in the wild. EPSS estimates a 5.8% chance of exploitation activity in the next 30 days, higher than 93% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-04-16.
- No fixed version is listed for TrueConf Client itself; fixed versions for the other affected products are listed on this page.
- Segment the networks that can reach it.
- Warn the people who use it, and filter files and links on the way in.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
- Update channels. The flaw sits between third-party code and your build or runtime.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.
Questions to answer about your own systems
- Where does TrueConf Client run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.