TrueConf CVE-2026-72529 is due today: close port 4307 and prove state

The signal and the facts that change the decision

The KEV deadline for CVE-2026-72529 arrives on 23 August. The vulnerability involves missing authentication and remote script execution in TrueConf Server through the service associated with port 4307, requiring direct confirmation of exposure and version.

The second TrueConf CVE has a later deadline, but both belong to the same product and investigation. The test should confirm network, application, and service state, not only change status.

Any prior exposure preserves the need to retain logs and hunt anomalous execution. A planned firewall rule or in-progress ticket does not reduce exposure until the rule is applied and tested externally.

Decision, limits, and stop condition

If the server cannot be proven fixed today, isolate the port and asset or withdraw the service until verifiable remediation exists.

A planned firewall rule or in-progress ticket does not reduce exposure until the rule is applied and tested externally.

Execution and proof of completion

Execution should start by rerunning internal and external discovery by port, service, dns, and inventory. Then, applying remediation or isolation and testing from an independent source. Closure requires also confirming cve-2026-72530 status and host investigation.

By end of day, every asset has version, port test, action, investigation, owner, and approved residual risk.

• rerunning internal and external discovery by port, service, DNS, and inventory.
• applying remediation or isolation and testing from an independent source.
• also confirming CVE-2026-72530 status and host investigation.
• By end of day, every asset has version, port test, action, investigation, owner, and approved residual risk.