CVE-2026-72530 was added to CISA's Known Exploited Vulnerabilities catalog on 20 August 2026, with a federal remediation deadline of 3 September. The vendor, TrueConf, shipped the fix in September across three release lines: 5.3.10, 5.4.10, and 5.5.6, for the Russian transportation, energy, IT, and electronics administrators the Head Mare hacktivist group has been targeting through the port-4307 chain since August. The blog post TrueConf wrote to announce the fix does not contain the CVE identifier. It does not contain the string "4307." It does not contain the words "sandbox" or "script." The sentence it chose instead is this: "Declining to install the updates will reduce the protection of your video collaboration system against potential hacker attacks via the public Internet."
CVE-2026-72530: TrueConf's September Advisory For This KEV-Listed Script-Sandbox Escape Names Neither The CVE Nor Port 4307.
vendor
patterns
cve
proof of concept
The chain is the design, not a bug
CVE-2026-72530 does not stand alone on port 4307. Public references describe it as the second of a two-CVE chain against TrueConf Server, paired with CVE-2026-72529. Both target the same service. The combined shape:
- CVE-2026-72529. Missing authentication on the script-submission surface. A remote caller with network access to 4307/TCP can submit a script for execution without presenting credentials.
- CVE-2026-72530. Script-sandbox escape in the service that executes the submitted scripts. NVD's description: "a specially crafted script to break out of the isolated environment and execute arbitrary code on the host system." Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Scope changed.PR:N: no privileges required.
Read together, the two NVD records describe a complete unauthenticated chain. The caller submits a script. The script runs in the sandbox. The script breaks the sandbox. The sandbox's job, per the design implied by the second CVE, was to contain the submitted scripts from reaching the host. It did not.
This is the Content Is Command shape at the service layer. Port 4307 is where external content (scripts a caller sends in) feeds a script interpreter (the one the sandbox was supposed to contain). The sandbox exists because the interpreter was never intended to be an attacker-facing one. The two CVEs together say: it is.
TrueConf's product documentation does not describe a scripting interface the vendor expects administrators to deliberately expose to the public Internet. Which is to say: the chain is not patching a misuse of a feature. It is patching the default configuration. The service runs by default. The port is open by default. The sandbox is the default protection. The sandbox is CVE-2026-72530.
The advisory is the void
TrueConf's September 2026 blog post, trueconf.com/blog/news/trueconf-server-security-update.html, is the vendor communication that exists for the KEV-listed chain. It announces the fix versions, 5.3.10, 5.4.10, and 5.5.6, and recommends upgrading. The blog does not contain the identifier CVE-2026-72530. The blog does not contain the identifier CVE-2026-72529. The blog does not contain the string "4307." The blog does not contain the words "sandbox," "script," or "authentication." The blog does not credit any external researcher for discovery. The blog does not reference CISA's KEV addition. The blog does not acknowledge in-wild exploitation by any threat actor.
The operative sentence, the one nested in the body of the announcement, is this:
Declining to install the updates will reduce the protection of your video collaboration system against potential hacker attacks via the public Internet.
Read it against the record. "Potential hacker attacks" is the vendor's name for an unauthenticated remote code execution chain used by a named APT against Russian critical infrastructure. "Via the public Internet" is the vendor's name for AV:N on both halves of the chain. "Reduce the protection" is the vendor's name for CVSS 9.0 and 9.8 on the same service. The sentence is literally true in every substring. It is written so that no substring can be quoted as an acknowledgment of what the patch addresses.
A TrueConf customer who opens the vendor's September blog, having been told by CISA to patch by 3 September, finds no CVE number to cross-reference against the KEV catalog. There is no vendor confirmation anywhere on trueconf.com that trueconf-server-security-update.html is the advisory for CVE-2026-72530. The link between the KEV entry and the vendor's blog exists only because the version numbers in the blog match the version numbers in the CVE record. The cross-reference is the customer's job.
This is the Disclosure After Exploitation pattern with a specific variant the house catalog has not yet named: the disclosure, when it finally lands, is engineered to be content-free. The CVE is documentation of the breach, per the pattern's canonical framing. The vendor's advisory, in this instance, is documentation of nothing.
The public PoC is a slideshow
The GitHub PoC repository the scanner surfaced for CVE-2026-72530, fevar54/CVE-2026-72530-TrueConf-Sandbox-Escape-, was created on 25 August 2026. The author pushed thirteen commits in seven minutes (16:14:36 to 16:21:17 Central Time) and did not touch the repository again. The star count is zero.
The commit that calls itself the proof of concept is e3facdc Add PoC for CVE-2026-72530 TrueConf Sandbox Escape. The file it added is poc/trueconf-sandbox-escape-poc.html. The file is 175 lines of HTML. The exploit code it contains is this JavaScript function:
function simulateAttack() {
const result = document.getElementById('result');
let steps = [
"📡 Conectando al puerto 4307...",
"✅ Conexión establecida con TrueConf Server",
"🔓 Bypass de autenticación (CVE-2026-72529)",
"💉 Inyectando script malicioso",
"🏃 Escape del sandbox (CVE-2026-72530)",
"🔥 Ejecución de código como SYSTEM",
"🕷️ Web shell instalado",
"📦 Trojanizado de instaladores TrueConf"
];
let i = 0;
const interval = setInterval(() => {
if (i < steps.length) {
const p = document.createElement('p');
p.textContent = steps[i];
result.appendChild(p);
i++;
} else {
clearInterval(interval);
// writes "SISTEMA COMPROMETIDO" in red to the DOM
}
}, 800);
}The function opens no socket. The function sends no packet. The function does not know what port 4307 is in any sense a program can use. The function is a setInterval that writes eight pre-authored strings to a <div>, one every 800 milliseconds, ending with "SISTEMA COMPROMETIDO" styled in red. The filename is trueconf-sandbox-escape-poc.html. The commit message is "Add PoC for CVE-2026-72530 TrueConf Sandbox Escape." A scanner polling GitHub for CVE-numbered repositories registers the file as evidence of a public exploit.
The remaining files complete the shape. src/network_security_config.sh is 19 lines of iptables -A INPUT -p tcp --dport 4307 -j DROP. iocs/cve-2026-72530_iocs.csv lists three C2 IPs and three C2 domains attributed to Head Mare, and then three rows whose Indicator column contains the literal string SHA-256 where a hash would be:
Hash,SHA-256,PhantomCore Backdoor,Head Mare APT
Hash,SHA-256,PhantomGraph Backdoor,Head Mare APT
Hash,SHA-256,Trojanized TrueConf Installer,Head Mare APTThe hashes themselves are absent. The YARA rule phantomcore_backdoor_trueconf matches any Windows PE binary containing three of nine strings including the literal substrings backdoor, cmd.exe, and powershell. The Sigma rule for web shell detection fires on Windows EventID 4688 command lines matching *wget* *4307*.
The file named License, at the repository root, is not a license. It opens with:
---
## 📄 **2. src/trueconf_sandbox_mitigation.py**
```python
#!/usr/bin/env python3
"""
CVE-2026-72530 - TrueConf Server Sandbox Escape Mitigation
The markdown says `2. src/trueconf_sandbox_mitigation.py`. The path `src/trueconf_sandbox_mitigation.py` does not exist in the repository. `git ls-tree -r HEAD` in `src/` returns one file, `network_security_config.sh`. The `2.` in the markdown heading implies a `1.` in the source document that was never committed. The Python body inside the License file, when read, is a port checker: `sock.connect_ex((self.target_ip, 4307))` followed by routines that print Spanish-language patch recommendations and write a JSON audit report.
This is the Phantom Project Documentation shape, in the house catalog's sense of the term. The License file is the chat-session paste where the operator did not clean up the markdown enumeration; the referenced path does not exist on disk; the only artifacts in the repository that claim to be exploits are a JavaScript DOM animation and a `socket.connect_ex` call. The scanner registered `has_pocs: true` on the repository because the repository's name contained the CVE string.
## Head Mare has the real exhibit
The chain's actual operator, per Kaspersky and ESecurity Planet reporting (both cited by name in the `reference` fields of the fevar54 repository's YARA rules), is Head Mare, the hacktivist group that has been attacking Russian organizations since 2024. The campaign's sector scope, per that reporting, is transportation, energy, IT, electronics, and software. The operational shape: Head Mare uses the port-4307 chain to establish code execution on the TrueConf Server itself. Head Mare drops the PhantomCore and PhantomGraph backdoors on the compromised host. Head Mare then substitutes trojanized TrueConf client installers on the server's download paths. Downstream users of the compromised server retrieve the installer; the installer carries the backdoor.
The TrueConf server is the pivot. The TrueConf client base is the target. A script-sandbox escape in the vendor's conferencing server is not interesting to Head Mare because it executes code on one host. It is interesting because the one host is where the clients download their updates from.
Head Mare has the hashes. Head Mare has the C2 infrastructure. Head Mare has working exploit code for both halves of the chain. None of this is in TrueConf's September advisory. The PhantomCore hashes are not in the fevar54 repository's IOC file, which declares them absent by writing `SHA-256` in the column where the hash would be. The only public artifact that attempts to catalog the campaign's operational indicators is a third party's threat intelligence. The only vendor artifact that speaks to TrueConf's customer base about the campaign is three sentences that do not contain the words "compromise," "exploitation," or "CVE."
## The record
Four facts belong to the public record on CVE-2026-72530. The chain is unauthenticated and reachable on 4307/TCP. The chain is being actively exploited by Head Mare against Russian critical infrastructure. The chain's fix was shipped by the vendor in September 2026. The vendor's disclosure of that fix contains no CVE number, no port, no mechanism, and no acknowledgment that the words "actively exploited" apply to what the patch addresses. A customer opening the vendor's blog after reading the KEV listing finds the fourth fact in place of the first three.
PoC: [fevar54/CVE-2026-72530-TrueConf-Sandbox-Escape-](https://github.com/fevar54/CVE-2026-72530-TrueConf-Sandbox-Escape-)Three of those facts a defender needs. One is the sentence the vendor chose to write instead.