CVE-2026-3502
Exploitation confirmed. First attested on 2026-04-02 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2026-03-30
- Fixed in8.5.3.884
- WeaknessCWE-494
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTCObserved activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-3502?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-3502?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.5 | < 8.5.3.884 | 8.5.3.884 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Trueconf to 8.5.3.884
- CISA’s required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.due 2026-04-16
Advisories and patches
- trueconf.comRelease Notes
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedfevar54/CVE-2026-3502---TrueConf-Client-Update-Hijacking-PoCfevar54/CVE-2026-3502-Scanner---TrueConf-Vulnerability-Detection-Tool PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2026-04-02
- Patch Due Date
- 2026-04-16
- Ransomware Use
- Unknown
- Required Action
- Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Sources
- NVDCVE recordread 2026-10-23
- CISA KEVKEV entry2026-04-02
- GCVEexploitation2026-04-02
- CISA-ADPSSVC decisionactive2026-04-02
- OpenCVESSVC decisionactive—
- CNACVSS 3.17.8read 2026-10-23
- CNAweakness (CWE)CWE-494read 2026-10-23
- FIRST EPSSEPSS score0.3 %2026-10-22
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L
- Published
- 2026-03-30
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-3502?
Is CVE-2026-3502 actively exploited?
What is the CVSS score for CVE-2026-3502?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.