What is CVE-2026-72530?

CVE-2026-72530 is TrueConf Server Code Injection Vulnerability. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-94 Code Injection.

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?

1 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 web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs 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-72530 using CVSS 9, EPSS 2%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. 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 KEVcriticalRemote Code Execpublic exploit

CVE-2026-72530

CVE-2026-72530 — TrueConf Server Code Injection Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-72530 in CISA KEV with required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

A remote unauthorized attacker with network access via port 4307/TCP to the TrueConf server versions 5.3.X to 5.3.9, 5.4.X to 5.4.9, 5.5.X to 5.5.5, and earlier could use a specially crafted script to break out of the isolated environment and execute arbitrary code on the host system.

Published Aug 19, 2026Updated Aug 19, 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 Aug 20, 2026

EPSS

ahead of 77% of scored CVEs

Affects

TrueConf

4 products listed

CVSS base

critical · 2 sources

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.

Update TrueConf server to versions 5.3.9, 5.4.9 or 5.5.5.

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Federal deadline Sep 3, 2026 — passed 18 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 Server	* to < 5.3	Vulnerable
TrueConf	TrueConf Server	5.3 to < 5.3.9	Vulnerable
TrueConf	TrueConf Server	5.4 to < 5.4.9	Vulnerable
TrueConf	TrueConf Server	5.5 to < 5.5.5	Vulnerable

Attack characteristics

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

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

None

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
9	CVSS 3.1	critical	2.2	6	kaspersky.com (CNA), TrueConf (CNA)
9.5	CVSS 4.0	critical	—	—	TrueConf (CNA)

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

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-94 · Improper Control of Generation of Code ('Code Injection')

Bypass Protection Mechanism
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands
Hide Activities

Mitigation: Refactor your program so that you do not have to dynamically generate code.

Weakness & attack patterns

CWE-94Code Injection

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

CAPEC-242 · Code InjectionCAPEC-77 · Manipulating User-Controlled VariablesCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1027.006Obfuscated Files or Information: HTML Smuggling
T1027.009Obfuscated Files or Information: Embedded Payloads
T1564.009Hide Artifacts: Resource Forking

CISA KEV details

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

CISAThat month →

Listed

Aug 20, 2026

Federal deadline

Sep 3, 2026

passed 18 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

Detection

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

Search application, proxy, and WAF logs for requests touching /TCP.
Prioritize edge telemetry for network-reachable TrueConf Server.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

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

2026
Added to CISA KEV catalog
Aug 20, 2026 · CISA
Added · CVSS 3.1 9.0 (AV:N)
Aug 19, 2026 · NVD
Initial · CVE published
Aug 19, 2026 · NVD
Reported · Advisory published by Kaspersky ICS CERT
Aug 7, 2026 · TrueConf
Reported · Issue confirmed by TrueConf
Aug 4, 2026 · TrueConf
Issue discovered by Kaspersky ICS CERT and reported to TrueConf
Aug 3, 2026 · TrueConf

References

7 on the record

ics-cert.kaspersky.com/advisories/2026/08/11/trueconf-server-breakout-from-isolated-environment/
Vendor Advisory
securelist.com/tr/head-mare-targets-trueconf-server-with-phantomcore/120988/
Vendor Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-72530
US Government Resource
trueconf.com/blog/news/security-fixes-updates-and-advisories
Vendor Advisory
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2026-72530
Vendor Advisory

Elsewhere on this site

TrueConfevery CVE for this vendor
August 2026what else CISA listed
Remote Code Execsame class
CWE-94other 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.

No confirmed IOCs, IP addresses, domains, file hashes, or malware 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-72530 is TrueConf Server Code Injection Vulnerability, a critical vulnerability affecting TrueConf Server from TrueConf. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 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 9 describes technical severity, while EPSS 2% 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.