CVE-2017-11506: When linking a Nessus scanner or agent to Tenable.io or other manager, Nessus 6.x before 6.11 does not veri...

Security readout for executives and security teams

Nessus 6.x before 6.11 could trust the wrong manager during initial scanner or agent linking because it did not verify the manager TLS certificate. A network-positioned attacker could potentially intercept that first connection. The sources do not report active exploitation. Exposure is limited to environments using Nessus 6.x before 6.11, especially during scanner or agent linking to Tenable.io or another manager across networks where interception is plausible. Treat as a targeted infrastructure integrity issue, not a broad internet worm risk. Prioritize remediation where Nessus scanners or agents were linked before version 6.11 or across less trusted networks. Mitigation focus: Upgrade Nessus 6.x deployments to 6.11 or later.; Follow Tenable advisory TNS-2017-11 for vendor remediation guidance.; Avoid linking scanners or agents across untrusted networks..

Prepared

Jun 12, 2026, 21:41 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.