CVE-2026-3502
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves tampering with the update delivery path, which is not described as using HTTP, so it likely uses another network protocol. Such tampering cannot be reliably detected or blocked by a web application firewall.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-3502 being exploited?
Yes. CVE-2026-3502 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-3502?
CVE-2026-3502 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-3502?
Yes. A fix has been recorded for CVE-2026-3502. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-3502 affect?
CVE-2026-3502 affects trueconf:trueconf. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affectedTrueConf Client versions 8.1.0 through 8.5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 31 Mar 2026 (SSVC 2.0.3).
timeline
- 30 Mar 2026Published
- 31 Mar 2026CISA SSVC assessment: exploitation active · same day later
- 2 Apr 2026Added to CISA KEV (exploited in the wild) · 2 days later
- 3 Apr 2026CVE record last updated · 1 day later
- 4 Apr 2026First proof-of-concept repository on GitHub (unvetted) · 1 day later
- 16 Apr 2026CISA remediation due date (US federal agencies) · 12 days later
- 2 Nov 2026Analysed by vulneraibility.com · 201 days (about 7 months) later
- Advisoryresearch.checkpoint.com /2026/operation-truechaos-0-day-exploitation-against-southeast-asian-government-
- Linktrueconf.com /blog/update/trueconf-8-5
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-3502
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.