Answer in brief
CVE-2026-3502 records a High severity vulnerability in TrueConf Client Update Integrity Verification Bypass. The current sources mark it as known exploited. The current feed maps TrueConf/TrueConf Client (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps TrueConf/TrueConf Client (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| TrueConf/TrueConf Clientgeneric | TrueConf Client versions 8.1.0 through 8.5.2 | Not reported |
Published upstream
Mar 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Apr 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Apr 2, 2026
Evidence: source:kev:kev:kev:recordTrueConf 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.
Quoted source text, attributed separately from HOL analysis.