dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 Apr 2026.
TrueconfApplication

CVE-2026-3502

HIGH · 7.8 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 8.5.3.884 or later.
See remediation →
94/100
Remediation priority · Urgent
In the wild

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

TrueConf Client downloads and applies application updates without verifying the integrity of the update payload. The updater lacks cryptographic signature or checksum validation, allowing an attacker with network positioning (e.g., MITM) or path control to substitute a malicious update that executes arbitrary code during the update process.

MitigationImplement cryptographic signature verification for all update packages before execution, using code signing certificates and validating signatures in the updater before applying any updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TrueconfApplication
Affected:< 8.5.3.884

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed TrueConf Client version
    Open TrueConf Client, go to Help > About, or run: trueconf_client --version, or check the installed programs list in Windows Control Panel > Programs and Features
    Affected if The installed version is less than 8.5.3.884 (e.g., 8.5.2, 8.5.1, etc.)
  2. Verify if update functionality is configured
    Check TrueConf Client settings for any update or auto-update configuration. Look in Preferences > Updates or Settings > Network for update-related options
    Affected if Update functionality is enabled and pointing to an update server
  3. Inspect update server configuration
    Check the client configuration files or registry for update server URL settings. Look for entries like UpdateServer, UpdateURL, or similar in the TrueConf config directory or Windows registry under HKLM\SOFTWARE\TrueConf
    Affected if An update server URL is configured and reachable from the client machine
  4. Confirm network position for man-in-the-middle risk
    Review network configuration and proxy settings used by TrueConf Client. Check if the update connection uses HTTPS or an unencrypted protocol
    Affected if The update connection uses unencrypted HTTP or weak TLS configuration

A user is affected if TrueConf Client version is below 8.5.3.884 AND the update feature is enabled, allowing potential injection of malicious updates during the update download process.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.5.3.884 or later
Fixed in 8.5.3.884
Interim mitigation

Implement cryptographic signature verification for all update packages before execution, using code signing certificates and validating signatures in the updater before applying any updates.

Recommended fix Moderate confidence

Trueconf Client 8.5.3.884 or later

  1. 1. Verify the current Trueconf Client version by accessing Help > About in the application menu
  2. 2. Navigate to the official Trueconf download page at https://trueconf.com/downloads or use the built-in update checker
  3. 3. Download Trueconf Client version 8.5.3.884 or the latest stable release available
  4. 4. Close the Trueconf application if currently running
  5. 5. Run the installer and follow the on-screen prompts to complete the update
  6. 6. After installation, verify the new version by checking Help > About to confirm the update was successful

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Trueconf Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3502 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data