Bug Fixes

Bug Fix	Defect ID
Fixed an issue that caused Tenable Nessus Manager to report the previously installed version of the plugin set on a linked agent. This fix also requires Tenable Agent version 11.2.0 or later.	02317032, 02304552, 02503048, 02507161
Fixed an issue where cluster-based agent scans started but did not complete. For database records of these incomplete scans, the cleanup process now correctly considers their associated files as "in use" and preserves them.	02430539
Fixed an issue where the host_time_minutes parameter triggered immediately for a host, which caused the scan for that host to abort.	02441109
Fixed an issue where the ssl_cipher_list preference did not control the TLS 1.3 cipher suites.	02510984
Upgrade Notes

• Tenable One Vulnerability Management FedRAMP environments support Tenable Nessus scanners versions 10.5.0 and later.
• If you are connecting to Tenable One Vulnerability Management through Tenable Nessus scanners, Tenable Agents, Tenable One Web App Scanning scanners, or Tenable Network Monitors (NNM) located in mainland China, you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.
• You can upgrade to the latest version of Tenable Nessus from any previously supported version.
• If your upgrade path skips versions of Tenable Nessus, Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.
• If you want your scanners to update to the newest version before the GA date automatically, set your Tenable Nessus Update Plan to Opt in to Early Access releases.
• If you want to update your scanners to the latest version before the GA date manually, disable automatic updates so the scanner does not automatically downgrade to the previous version.