Patch & vulnerability status
Nessus Agent 11.2.2
Latest tracked version 11.2.2. Release status, tracked CVEs, and automated cross-platform patching for Nessus Agent.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 11.2.2 | 10 | 2026-08-10 |
Known vulnerabilities (CVEs) in Nessus Agent
Lavawall tracks 10 published CVEs affecting Nessus Agent, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2026-2026 | 2026-02-13 17:16:14 | MEDIUM (5) | A vulnerability has been identified where weak file permissions in the Nessus Agent directory on Windows hosts could allow unauthorized access, potentially permitting Denial of Service (DoS) attacks. | LOCAL |
| CVE-2025-36633 | 2025-06-13 15:15:20 | HIGH (9) | In Tenable Agent versions prior to 10.8.5 on a Windows host, it was found that a non-administrative user could arbitrarily delete local system files with SYSTEM privilege, potentially leading to local privilege escalation. | LOCAL |
| CVE-2025-36632 | 2025-06-16 14:15:22 | HIGH (8) | In Tenable Agent versions prior to 10.8.5 on a Windows host, it was found that a non-administrative user could execute code with SYSTEM privilege. | LOCAL |
| CVE-2025-36631 | 2025-06-13 15:15:20 | HIGH (8) | In Tenable Agent versions prior to 10.8.5 on a Windows host, it was found that a non-administrative user could overwrite arbitrary local system files with log content at SYSTEM privilege. | LOCAL |
| CVE-2023-5847 | 2023-11-01 16:15:09 | MEDIUM (7) | Under certain conditions, a low privileged attacker could load a specially crafted file during installation or upgrade to escalate privileges on Windows and Linux hosts. | LOCAL |
| CVE-2021-3450 | 2021-03-25 15:15:14 | HIGH (7) | The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. All of the named "purpose" values implemented in libcrypto perform this check. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. In order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j). | NETWORK |
| CVE-2021-20118 | 2021-09-09 12:15:09 | MEDIUM (7) | Nessus Agent 8.3.0 and earlier was found to contain a local privilege escalation vulnerability which could allow an authenticated, local administrator to run specific executables on the Nessus Agent host. This is different than CVE-2021-20117. | LOCAL |
| CVE-2021-20117 | 2021-09-09 12:15:08 | MEDIUM (7) | Nessus Agent 8.3.0 and earlier was found to contain a local privilege escalation vulnerability which could allow an authenticated, local administrator to run specific executables on the Nessus Agent host. This is different than CVE-2021-20118. | LOCAL |
| CVE-2021-20077 | 2021-03-19 19:15:13 | MEDIUM (7) | Nessus Agent versions 7.2.0 through 8.2.2 were found to inadvertently capture the IAM role security token on the local host during initial linking of the Nessus Agent when installed on an Amazon EC2 instance. This could allow a privileged attacker to obtain the token. | LOCAL |
| CVE-2020-5793 | 2020-11-05 20:15:17 | HIGH (8) | A vulnerability in Nessus versions 8.9.0 through 8.12.0 for Windows & Nessus Agent 8.0.0 and 8.1.0 for Windows could allow an authenticated local attacker to copy user-supplied files to a specially constructed path in a specifically named user directory. An attacker could exploit this vulnerability by creating a malicious file and copying the file to a system directory. The attacker needs valid credentials on the Windows system to exploit this vulnerability. | LOCAL |
Why keeping Nessus Agent patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every Nessus Agent release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches Nessus Agent
Lavawall® watches Nessus Agent releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on Nessus Agent, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
What is the latest version of Nessus Agent?
Lavawall tracks Nessus Agent at version 11.2.2 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks Nessus Agent at version 11.2.2 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Does Nessus Agent have known security vulnerabilities (CVEs)?
Lavawall tracks 10 CVEs for Nessus Agent and remediates them automatically as part of patching.
Lavawall tracks 10 CVEs for Nessus Agent and remediates them automatically as part of patching.
How do I patch Nessus Agent automatically?
Deploy the Lavawall® agent and Nessus Agent updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Deploy the Lavawall® agent and Nessus Agent updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for Nessus Agent through public information and proprietary statistical analysis, and can patch it automatically across your fleet.