CVE-2026-72529 — Trueconf Server
CRITICALCVE-2026-72529 is a critical-severity (CVSS 9.8) Missing Authentication vulnerability in trueconf trueconf server. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-08-20) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
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 execute an arbitrary…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-08-20. Federal agencies were required to remediate by 2026-08-23.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-72529.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-72529 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,574 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
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 execute an arbitrary script by calling an undocumented function.
Affected Products
trueconf servertrueconfDetection & mitigation playbook
Vendor / applianceDetect
Inventory every trueconf trueconf server deployment and check each version against the affected-products list above.
Fix
Apply the trueconf trueconf server security patch or hotfix for CVE-2026-72529 on the affected version, following the vendor advisory for your exact build.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-72529 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.