What is CVE-2026-3502?

CVE-2026-3502 is TrueConf Client Update Integrity Verification Bypass. The supplied enrichment data classifies it as Unclassified mapped to CWE-494 CWE-494.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

14 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-3502 using CVSS 7.8, EPSS 6%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Head Mare (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighpublic exploit

CVE-2026-3502

CVE-2026-3502 — TrueConf Client Update Integrity Verification Bypass

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-3502 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Mar 30, 2026Updated Jun 17, 2026Sources: NVD, TrueConf (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Apr 2, 2026

EPSS

ahead of 93% of scored CVEs

Affects

TrueConf

TrueConf Client

CVSS base

7.8

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade TrueConf Client to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA 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.

Federal deadline Apr 16, 2026 — passed 155 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
TrueConf	TrueConf Client	TrueConf Client versions 8.1.0 through 8.5.2	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Adjacent

Privileges Req

High

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.8	CVSS 3.1	high	1.2	6	checkpoint.com (CNA), TrueConf (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-494 · Download of Code Without Integrity Check

Execute Unauthorized Code or Commands
Alter Execution Logic
Other

Mitigation: Perform proper forward and reverse DNS lookups to detect DNS spoofing.

Weakness & attack patterns

CWE-494

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-185 · Malicious Software DownloadCAPEC-187 · Malicious Automated Software UpdateCAPEC-186 · Malicious Software UpdateCAPEC-184 · Software Integrity AttackCAPEC-533 · Malicious Manual Software Update

T1195.002Supply Chain Compromise: Compromise Software Supply Chain
T1072Software Deployment Tools
T1195.001Supply Chain Compromise: Software Dependencies and Development Tools

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Apr 2, 2026

Federal deadline

Apr 16, 2026

passed 155 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 14 public PoC repositories were reported.

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Head Mare

hash22e32bcf113326e366ac480b077067cf85
AlienVault OTX Feeds · Mar 31, 2026
hash9b435ad985b733b64a6d5f39080f4ae088
AlienVault OTX Feeds · Mar 31, 2026
hash248a4d7d4c48478dcbeade8f7dba80b385
AlienVault OTX Feeds · Mar 31, 2026

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.8 (AV:A)
Jun 17, 2026 · NVD
Cve is exploited fevar54/CVE-2026-3502---TrueConf-Client-Update-Hijacking-PoC
Apr 5, 2026 · SOCRadar CTI
Added to CISA KEV catalog
Apr 2, 2026 · CISA
Initial · CVE published
Mar 30, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

17×SvrsApr 1, 2026 – Aug 9, 2026 · SOCRadar CTI
12×TweetsApr 2, 2026 – Aug 13, 2026 · SOCRadar CTI
2×Github ReposApr 4, 2026 · SOCRadar CTI
2×ModifiedApr 2, 2026 – Apr 3, 2026 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelApr 6, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Apr 1, 2026 · SOCRadar CTI

References

5 on the record

trueconf.com/blog/update/trueconf-8-5
Product, Release Notes, NIST, Vendor Advisory
research.checkpoint.com/2026/operation-truechaos-0-day-exploitation-against-southeast-asian-government-targets/
Third Party Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-3502
US Government Resource, NIST
trueconf.com/downloads/windows.html
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-3502
Vendor Advisory

Coverage

17 stories from the feeds we poll

12 more reports on this CVEShowing 5 of 17 · Vendor research and security press coverageUnlock free

Elsewhere on this site

TrueConfevery CVE for this vendor
April 2026what else CISA listed
Unclassifiedsame class
CWE-494other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 3 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-3502 is TrueConf Client Update Integrity Verification Bypass, a high vulnerability affecting TrueConf Client from TrueConf. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 14 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.8 describes technical severity, while EPSS 6% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.