# CVE-2026-3502: TrueConf Client Download of Code Without Integrity Check

> Attackers can execute arbitrary code by substituting tampered update payloads due to missing integrity verification in TrueConf Client updates.

- **Severity:** High 7.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Yes, since 2 Apr 2026 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-33r5-g5m3-5m79

## What is CVE-2026-3502?

CVE-2026-3502 is a high-severity vulnerability in TrueConf Client, published on 30 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-3502?

It affects 1 product.


Products: Trueconf Trueconf.

## How do I fix CVE-2026-3502?

No fix has been published for CVE-2026-3502 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 16 Apr 2026.

## Is CVE-2026-3502 being exploited?

Yes. Attackers have exploited CVE-2026-3502 in the wild since at least 2 Apr 2026.

Public exploit code:

- PoC de CVE-2026-3502: hijacking de actualizacion en TrueConf Client para RCE (Operacion TrueChaos). (github_poc): https://github.com/fevar54/CVE-2026-3502---TrueConf-Client-Update-Hijacking-PoC
- Scanner de CVE-2026-3502: detecta clientes TrueConf vulnerables e IOCs de TrueChaos. Reportes JSON/HTML/CSV. (github_poc): https://github.com/fevar54/CVE-2026-3502-Scanner---TrueConf-Vulnerability-Detection-Tool

## Other vulnerabilities in TrueConf Client

- [CVE-2025-66835](https://insights.sbomify.com/CVE-2025-66835/): Other in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3502 and fix it if it is affected.

What it is: CVE-2026-3502 is a high-severity vulnerability in TrueConf Client, published on 30 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-3502 in the wild since at least 2 Apr 2026.

Affected product: TrueConf Client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3502/ (Markdown: https://insights.sbomify.com/CVE-2026-3502/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3502
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3502
- OSV: https://osv.dev/vulnerability/CVE-2026-3502

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3502/
Summaries are generated and may contain mistakes; the official description above is the record.