Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Evidence dossier
CVE-2026-3502
TrueConf Client Update Integrity Verification Bypass
gen-56ccdaf9Normalized restatement
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.
- State
- PUBLISHED
- Published
- Mar 30, 2026
- Updated
- Apr 3, 2026
- Evidence coverage
- 85%
2026-07-18 · v2026.06.15 · percentile 92.2%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
TrueConf Client Update Integrity Verification Bypass
TrueConf Client Download of Code Without Integrity Check Vulnerability
Probability 0.057500000000; percentile 0.922270000000
Applicability
Cited product scope
[{"status": "affected", "version": "TrueConf Client versions 8.1.0 through 8.5.2"}]unknowncpe:2.3:a:trueconf:trueconf:*:*:*:*:*:windows:*:*; end excluding 8.5.3.884supportedAssessments
CVSS by origin
CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:LCVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:LLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.