{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-24916 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-24916 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24916 is a high-severity vulnerability in Tenable Network Monitor, published on 23 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-24916 and fix it if it is affected.\n\nWhat it is: CVE-2025-24916 is a high-severity vulnerability in Tenable Network Monitor, published on 23 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-24916 in the wild and no public exploit code.\n\nAffected product: Tenable Network Monitor. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-24916/ (Markdown: https://insights.sbomify.com/CVE-2025-24916/index.md)","id":"CVE-2025-24916","markdown":"https://insights.sbomify.com/CVE-2025-24916/index.md","name":"CVE-2025-24916","record":{"aliases":["GHSA-9wpx-f5qr-7rcr"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Network Monitor","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges if Tenable Network Monitor is installed to a non-default location with insecure permissions.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"tenable","cpe":[{"product":"nessus_network_monitor","vendor":"tenable"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"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 installation location.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Improper Access Control leads to Local Priviledge Escalation","id":"CVE-2025-24916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Access Control leads to Local Privilege Escalation","id":"CVE-2025-24917"},"packages":[],"prev":{"headline":"Privilege escalation in Nessus Agent","id":"CVE-2025-24915"},"products":["Network Monitor"],"published":"2025-05-23","related":[{"cvss_score":8.4,"headline":"XSS","id":"CVE-2024-9158","kev_date_added":null,"published":"2024-09-30"},{"cvss_score":7.8,"headline":"Improper Access Control leads to Local Privilege Escalation","id":"CVE-2025-24917","kev_date_added":null,"published":"2025-05-23"},{"cvss_score":7.8,"headline":"Path traversal in Nessus Network Monitor","id":"CVE-2020-5794","kev_date_added":null,"published":"2020-11-06"},{"cvss_score":7.2,"headline":"Blind SQL Injection","id":"CVE-2023-5624","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":7.1,"headline":"Privilege Escalation","id":"CVE-2023-5622","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":7,"headline":"Privilege Escalation","id":"CVE-2023-5623","kev_date_added":null,"published":"2023-10-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Tenable"]},"summary":"Local attackers can escalate privileges if Tenable Network Monitor is installed to a non-default location with insecure permissions.","url":"https://insights.sbomify.com/CVE-2025-24916/"}