The following are new features included in Tenable Agent 10.9.0:$$$$$$Introduced agent safe mode; which instructs an agent to maintain connection with its manager in the event of an operational error.$$$$$$Enabled agents to have their plugins reset from the management console.$$$$$$Enabled agents to have their local plugin databases recompiled from the management console.

Tenable Nessus Agent 10.8.4 (2025-04-08)$$$OpenBug Fixes$$$Bug Fixes$$$Addressed an issue in the Windows MSI installer that allowed a user to permanently disable the agent if the installation was canceled in a custom (non-default) directory with overly-broad permissions.$$$OpenUpgrade Notes$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.

Bug Fix$$$Fixed an uncommon issue that caused agents to crash when certain error conditions were logged.$$$Fixed an issue that caused some agents running versions 10.8.0 or 10.8.1 to go offline following a differential plugin update.$$$For more details refer - https://docs.tenable.com/release-notes/Content/nessus-agent/2025.htm#Tenable-Nessus-Agent-10.8.2-(2025-01-02)

Tenable Nessus Agent 10.8.1 (2024-11-26)$$$ClosedBug Fixes$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.8.0 (2024-11-12)$$$OpenNew Features$$$The following are new features included in Tenable Nessus Agent 10.8.0:$$$$$$Continuous assessment scanning for Linux.$$$$$$Agents that are installed on Linux hosts and linked to Tenable Vulnerability Management now support the continuous assessment scanning feature. Continuous assessment scanning enables continuous software inventory monitoring on the host and is configurable via agent profiles in the Tenable Vulnerability Management user interface.$$$$$$Continuous assessment scanning is not compatible with agents on which NIAP mode is enforced.$$$$$$For more information; see Agent Continuous Assessment Scanning in the Tenable Vulnerability Management User Guide.$$$$$$OpenChanged Functionality and Performance Enhancements$$$The following enhancements are included in Tenable Nessus Agent 10.8.0:$$$$$$Improved debug output by capturing software library details.$$$$$$Improved logging for nessus-service on Windows.$$$$$$Improved performance of plugin compilation.$$$$$$Agents no longer support TLS versions 1.1 and earlier.$$$$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Fixed an issue that caused some agents to create orphaned processes when stopping or pausing a scan.t02063481$$$Fixed SSL errors that occurred when using the nessuscli command line flag --reset-all to create a fresh agent image.t02054662$$$Removed support for nessusd command line option for setting a master password (-K).t02034977$$$Updated the Plugin Disk Usage health alert threshold to a more appropriate value.t02090915; 02088697; 02089271; 02104953$$$Fixed an issue that prevented some agents from being stopped or restarted after an upgrade.t01715462; 01786230; 01921503$$$Fixed an issue that caused agents to crash on x86/x86_64 hardware that lacked the x86 crc32 instruction (for example; very old AMD processors).t02097974$$$OpenSupported Platforms$$$The following are supported platform updates made in Tenable Nessus Agent 10.8.0:$$$$$$Added support for the following platforms:$$$$$$Fedora 40$$$$$$Windows Server 2025$$$$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.7.2 (2024-07-25)$$$OpenChanged Functionality and Performance Enhancements$$$The following enhancements are included in Tenable Nessus Agent 10.7.2:$$$$$$The time elapsed since scan execution completed when uploading a triggered scan result is now provided to the user.$$$$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Reduced physical memory usage (RSS) at the time of plugin set updates.t02011617$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.7.2 (2024-07-25)$$$OpenChanged Functionality and Performance Enhancements$$$The following enhancements are included in Tenable Nessus Agent 10.7.2:$$$$$$The time elapsed since scan execution completed when uploading a triggered scan result is now provided to the user.$$$$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Reduced physical memory usage (RSS) at the time of plugin set updates.t02011617$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.7.1 (2024-07-02)$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Tenable Nessus Agent no longer uses Transparent Huge Pages on Linux systems by default.t02011617$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.6.4 (2024-05-16)$$$OpenSecurity Updates$$$The following are security updates included in Tenable Nessus Agent 10.6.4:$$$$$$Addressed a vulnerability that allowed low-privileged users to exploit a Time-of-Check to Time-of-Use (TOCTOU) race condition vulnerability during the Windows Tenable Nessus Agent installation process.$$$$$$Addressed a vulnerability in which the Windows Tenable Nessus Agent setup process could have failed to set proper access rights for the installation folder if you chose a custom installation path during installation.$$$$$$For more information; see the Tenable Product Security Advisory.$$$$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Starting with Tenable Nessus Agent 8.1.0; Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.6.3 (2024-05-02)$$$$$$OpenChanged Functionality and Performance Enhancements$$$$$$The following enhancements are included in Tenable Nessus Agent 10.6.3:$$$$$$Eliminated redundant metadata uploads from Tenable Nessus Agent to Tenable Vulnerability Management during the early stages of a scan.$$$$$$Removed nessusd.dump entries that show the message: Error: function get_int() has no argument key.$$$$$$OpenBug Fixes$$$$$$Bug FixtDefect ID$$$Enhanced Tenable Nessus Agents capability to recover from operating on a system with an incorrect future time setting. This improvement prevents potential software and plugin update failures.t01919946$$$$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Starting with Tenable Nessus Agent 8.1.0; Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.6.2 (2024-04-15)$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Prevented a scenario in which multiple simultaneous scans assigned to an agent that has not retrieved plugins yet could execute without plugins.t01785607$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Starting with Tenable Nessus Agent 8.1.0; Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.6.1 (2024-04-05)$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Fixed an issue that caused agents to restart when certain DNS errors occurred.t01851304; 01896427$$$Fixed an issue where a small subset of executable files of agents installed on Windows systems did not have digital signatures.t01875389$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; Tenable Web App Scanning scanners; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Starting with Tenable Nessus Agent 8.1.0; Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 2024 Release Notes$$$Tenable Nessus Agent 10.5.1 (2024-01-10)$$$Bug Fixt Defect ID$$$Fixed an issue that caused download failures while using incremental delays.t01701708$$$$$$Upgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Starting with Tenable Nessus Agent 8.1.0; Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.5.0 (2023-12-12)$$$OpenNew Features$$$The following are new features included in Tenable Nessus Agent 10.5.0:$$$$$$Added support for differential scan reporting: a future Tenable Vulnerability Management feature.$$$$$$OpenChanged Functionality and Performance Enhancements$$$The following enhancements are included in Tenable Nessus Agent 10.5.0:$$$$$$Improved agent plugin download logic when launching staggered scans.$$$$$$OpenBug Fixes$$$Bug FixtDefect ID$$$Fixed a permissions issues that caused automatic upgrades to fail on SELinux-enabled systems.t01630995; 01709066$$$Fixed an issue that caused the agent service to stop after automatic upgrades on Unix systems.t01675402; 01659798$$$ClosedSupported Platforms$$$OpenUpgrade Notes$$$If you are connecting to Tenable Vulnerability Management through Tenable Nessus scanners; Tenable Nessus Agents; or Tenable Nessus Network Monitors (NNM) located in mainland China; you must connect through sensor.cloud.tenablecloud.cn instead of sensor.cloud.tenable.com.$$$$$$New Tenable Vulnerability Management Domain - As a part of continuous security and scalability improvements to Tenable infrastructure; we have added a new sensor.cloud.tenable.com domain that Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with.$$$$$$Starting with Tenable Nessus Agent 8.1.0; Tenable Vulnerability Management-linked Tenable Nessus Agents communicate with Tenable Vulnerability Management using sensor.cloud.tenable.com. If agents versions 8.1.0 through 10.3.1 are not able to connect to the new domain; they fall back to using cloud.tenable.com. Tenable Nessus Agent 10.3.2 and later do not fall back using the cloud.tenable.com domain.$$$$$$Recommended Action: If you use domain allow lists for firewalls; Tenable recommends adding *.cloud.tenable.com (with the wildcard character) to the allow list. This ensures communication with sensor.cloud.tenable.com and all future subdomains; reducing operational overhead. Contact your network administrator for assistance with making necessary changes to your allow list.$$$You can upgrade to the latest version of Tenable Nessus Agent from any previously supported version.$$$If your upgrade path skips versions of the Tenable Nessus Agent; Tenable recommends reviewing the release notes for all skipped versions to learn about new features and bug fixes.

Tenable Nessus Agent 10.4.3 (2023-10-31)$$$OpenSecurity Updates$$$The following are security updates included in Tenable Nessus Agent 10.4.3:$$$$$$Updated OpenSSL to version 3.0.12.$$$Refer-https://www.tenable.com/security/tns-2023-38?_gl=1*13m9jsc*_ga*NzkxNjgzMDE2LjE2OTkyNTA5ODM.*_ga_HSJ1XWV6ND*MTY5OTI2MjE1My4yLjEuMTY5OTI2NTE4MS4wLjAuMA..