Threats / TrueConf / CVE-2026-3502
CVE-2026-3502
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
TrueConf Client vulnerability
TrueConf Client fails to verify integrity of downloaded updates, allowing attackers on the delivery path to inject malicious code executed with updater privileges.
Verdict
Today item — known-exploited.
An attacker positioned to intercept update traffic can replace legitimate updates with malicious payloads, achieving arbitrary code execution in the updater or user context without detection.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-04-02).
Probability (EPSS)
EPSS 0.0575 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: TrueConf, Client. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-494 Download Without Integrity Check — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I intercept or redirect the update download channel to serve a tampered payload instead of the legitimate update.
Business
The organization's endpoint security is compromised as malicious code executes with system or user privileges during the update process.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious update package that appears valid to the client but contains arbitrary executable code.
Business
Deployed systems become infected with attacker-controlled code, enabling data theft, lateral movement, or persistent compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute the injected code in the context of the updater process, which typically runs with elevated privileges.
Business
The attacker gains privileged access to the affected system, bypassing user-level security controls and enabling full system compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by checkpointCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.