<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: nessus network monitor</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-24917: In Tenable Network Monitor versions prior to 6.5.1 on a Windows host, it was found that a non-administrative u</title><link>https://patchthecve.com/cve/CVE-2025-24917.html</link><guid>https://patchthecve.com/cve/CVE-2025-24917.html</guid><pubDate>Wed, 17 Jun 2026 08:59:50 +0000</pubDate><description>HIGH 7.8: In Tenable Network Monitor versions prior to 6.5.1 on a Windows host, it was found that a non-administrative user could stage files in a local directory to run arbitrary code with SYSTEM privileges, potentially leading to local privilege escalation.</description></item><item><title>CVE-2025-24916: When installing Tenable Network Monitor to a non-default location on a Windows host, Tenable Network Monitor v</title><link>https://patchthecve.com/cve/CVE-2025-24916.html</link><guid>https://patchthecve.com/cve/CVE-2025-24916.html</guid><pubDate>Wed, 17 Jun 2026 08:59:50 +0000</pubDate><description>HIGH 7.0: When installing Tenable Network Monitor to a non-default location on a Windows host, Tenable Network Monitor versions prior to 6.5.1 did not enforce secure permissions for sub-directories. This could allow for local privilege escalation if users had not secured the directories in the non-default ins</description></item><item><title>CVE-2024-9158: A stored cross site scripting vulnerability exists in Nessus Network Monitor where an authenticated, privilege</title><link>https://patchthecve.com/cve/CVE-2024-9158.html</link><guid>https://patchthecve.com/cve/CVE-2024-9158.html</guid><pubDate>Wed, 17 Jun 2026 08:24:03 +0000</pubDate><description>HIGH 8.4: A stored cross site scripting vulnerability exists in Nessus Network Monitor where an authenticated, privileged local attacker could inject arbitrary code into the NNM UI via the local CLI.</description></item></channel></rss>