Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-3502: TrueConf Client Unverified Update Code Execution

Published Mar 30, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS5.8%93rd percentile
CISA KEVYesAdded Apr 2, 2026
In the wildActivePer CISA KEV
Vendor
Trueconf
IdentifiersCVE-2026-3502CWE-494 · Download of Code Without Integrity…

CVE-2026-3502 is a CVSS 7.8 vulnerability in the TrueConf Windows Client update-validation mechanism. The client retrieves update packages from a centrally managed on-premises TrueConf Server and applies them without adequate integrity and authenticity validation. An attacker able to control or tamper with the update source can substitute a malicious package for the legitimate client update, which is then delivered through the trusted update workflow. The issue was exploited as a zero-day in Operation TrueChaos against Southeast Asian government entities.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful attacker can cause arbitrary code execution on connected client endpoints in the security context of the updating process or logged-in user. Compromise of a central on-premises update source can enable malware distribution to multiple connected organizations and endpoints without separately compromising each client. Observed exploitation deployed the Havoc command-and-control framework and supported reconnaissance, persistence, privilege escalation, and follow-on payload delivery.

Mitigation

If you can’t patch tonight, do this now.

Until updates are fully deployed, restrict administrative and network access to on-premises TrueConf Server instances and protect the update-delivery path from unauthorized modification. Monitor for unexpected client-update prompts, anomalous update-package changes, and client-side execution originating from update activity. Investigate endpoints and update infrastructure for compromise where unverified updates may have been distributed. If vendor remediation or compensating controls cannot be applied, discontinue use of the affected product.

Remediation

Patch, then assume compromise.

Upgrade TrueConf Windows Client to version 8.5.3 or later, which includes the vendor’s fix released in March 2026. Identify and update all clients using earlier versions, particularly those configured to retrieve updates from on-premises TrueConf Server instances. Review and remediate potentially compromised on-premises TrueConf update servers before restoring update distribution.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-3502---TrueConf-Client-Update-Hijacking-PoCThis repository is a standalone Python exploit toolkit for a claimed TrueConf Windows update hijacking issue, CVE-2026-3502. It is not tied to a common exploit framework. The structure contains four main code files: `exploit.py` (primary exploit simulation and reporting), `detectors/vulnerability_checker.py` (server/client/IOC checker), `malicious_update_builder.py` (builder for a malicious update package using generated C stubs and an Inno Setup script), and `update_server.py` (Flask-based fake update server for MITM or server-compromise simulation). Supporting files include `README.md`, usage notes, requirements, and an example output file. Main exploit capability: `exploit.py` checks whether a target exposes `/downlods/trueconf_client.exe` and treats missing `ETag`/`Last-Modified` headers as evidence of weak integrity protection. It can then simulate an attack by validating a supplied malicious EXE, hashing it, printing deployment steps, and generating a JSON report. It does not automatically compromise the target server; instead, it operationalizes the attack workflow by documenting how to replace the server-hosted update binary in `C:\Program Files\TrueConf Server\ClientInstFiles\trueconf_client.exe`. The builder component is more aggressive: `malicious_update_builder.py` generates source for a DLL sideload payload (`7z-x64.dll`), an Inno Setup installer script, and decoy binaries. The generated installer script drops files under `C:\ProgramData\PowerISO`, launches a client binary, adds persistence via `HKCU\Software\Microsoft\Windows\CurrentVersion\Run\UpdateCheck`, and creates a scheduled task `TrueConfUpdate`. The DLL payload is demonstrative but includes a proof action writing `C:\ProgramData\pwned.txt`; comments reference downloading a Havoc payload from `http://attacker.com/havoc.exe`. `update_server.py` provides a fake TrueConf server with routes `/downlods/trueconf_client.exe`, `/config`, `/version.js`, and `/`, allowing an operator to serve a malicious update and spoof version metadata to clients. `detectors/vulnerability_checker.py` performs HEAD requests to the update endpoint, checks local Windows install paths for vulnerable client versions, and looks for IOC artifacts such as dropped files, Run keys, and scheduled-task references. Overall, this is an operational proof-of-concept repository for malicious update delivery in a Windows enterprise/internal-network scenario. It combines vulnerability checking, fake infrastructure, payload packaging, and deployment guidance. While some actions are simulated and several payload steps are instructional rather than fully automated, the repository clearly aims to demonstrate arbitrary code execution through update hijacking and includes persistence-oriented payload examples.fevar54 · Disclosed Apr 4, 2026 · python · c · network · web · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
TrueconfTrueconfapplication
FAQ

Frequently asked questions

Is CVE-2026-3502 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 2, 2026.
Is there a public exploit for CVE-2026-3502?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-3502, the earliest disclosed Apr 4, 2026.
Is there a patch for CVE-2026-3502?
Upgrade TrueConf Windows Client to version 8.5.3 or later, which includes the vendor’s fix released in March 2026. Identify and update all clients using earlier versions, particularly those configured to retrieve updates from on-premises TrueConf Server instances.
What products are affected by CVE-2026-3502?
Trueconf.
How severe is CVE-2026-3502?
CVE-2026-3502 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 5.8% (93rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

75 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+9 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware13Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity61Community discussion across Reddit, Mastodon, and other social sources.