# CVE-2026-82412: ntopng: Remote Code Execution via OS Command Injection in Vulnerability-Scan REST API

> Authenticated non-admin users or CSRF attacks can execute OS commands via the vulnerability-scan API in ntopng.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** AZL-103398, GHSA-2c6p-4pfj-qv58, UBUNTU-CVE-2026-82412

## What is CVE-2026-82412?

CVE-2026-82412 is a high-severity command injection vulnerability in ntopng, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ntopng is a web-based network traffic monitoring application. Prior to 6.7.260717, the vulnerability-scan endpoints scripts/lua/rest/v2/add/host/to_scan.lua and scripts/lua/rest/v2/exec/host/schedule_vulnerability_scan.lua accept the scan_ports parameter without an administrator gate and pass it through validateSingleWord, which permits shell metacharacters. scripts/lua/modules/vulnerability_scan/vs_utils.lua then concatenates scan_ports into an nmap command in nmap_scan_host and executes the command through ntop.execCmd or ntop.execCmdAsync and popen. Any authenticated non-admin user can execute operating-system commands as the ntopng process account when nmap is available. Because the endpoints accept GET requests while ntopng's CSRF validation applies to POST request bodies, an attacker can also trigger the command through a logged-in user's browser without possessing ntopng credentials. This issue is fixed in version 6.7.260717.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-82412?


## How do I fix CVE-2026-82412?

No fix has been published for CVE-2026-82412 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82412 being exploited?

There is no known exploitation of CVE-2026-82412 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82412 and fix it if it is affected.

What it is: CVE-2026-82412 is a high-severity command injection vulnerability in ntopng, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82412 in the wild and no public exploit code.

Affected product: ntopng. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82412/ (Markdown: https://insights.sbomify.com/CVE-2026-82412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82412
- OSV: https://osv.dev/vulnerability/CVE-2026-82412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82412/
Summaries are generated and may contain mistakes; the official description above is the record.