CVE-2026-82412

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-83982 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 21, 2026

Last Modified

September 23, 2026

Advisory Details (5)

Auto-updated Sep 21, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit 9f42a12251d8 (ntop/ntopng)

Fix landed in ntop/ntopng commit 9f42a12251d8 — awaiting tagged release

https://github.com/ntop/ntopng/commit/9f42a12251d881e3a20ebd667c1a2e6a6570c270
GitHub commit

commit 838ccd523a3d (ntop/ntopng)

Fix landed in ntop/ntopng commit 838ccd523a3d — awaiting tagged release

https://github.com/ntop/ntopng/commit/838ccd523a3d4a71b29a62f7653e572a1ffa5cf6
GitHub commit

commit 771b34a9d37f (ntop/ntopng)

Fix landed in ntop/ntopng commit 771b34a9d37f — awaiting tagged release

https://github.com/ntop/ntopng/commit/771b34a9d37f5de989eec4f2f8f2e852db1c7e5e
GitHub commit

commit 0d3156274f4d (ntop/ntopng)

Fix landed in ntop/ntopng commit 0d3156274f4d — awaiting tagged release

https://github.com/ntop/ntopng/commit/0d3156274f4d12db8b61432ebeded10966c01f3e
GitHub advisoryMentions a patch (unverified)

Remote Code Execution via OS Command Injection in Vulnerability-Scan REST API · Advisory · ntop/ntopng · GitHub

https://github.com/ntop/ntopng/security/advisories/GHSA-2c6p-4pfj-qv58

Vendor Advisories for CVE-2026-82412(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 115 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-27 18:52 UTCEG score recompute
  8. 2026-10-27 18:52 UTCVendor advisory
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-25 13:58 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-20 07:45 UTCEG score recompute
  19. 2026-10-20 07:45 UTCVendor advisory
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-10-18 03:08 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 75 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  3. 2026-10-13 06:03 UTCEG score recompute
  4. 2026-10-13 06:03 UTCVendor advisory
  5. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  6. 2026-10-12 14:55 UTCEG score recompute
  7. 2026-10-12 02:03 UTCVendor advisory
  8. 2026-10-11 19:19 UTCEG score recompute
  9. 2026-10-11 16:36 UTCEG score recompute
  10. 2026-10-11 13:55 UTCVendor advisory
  11. 2026-10-11 13:54 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-10-11 01:48 UTCEG score recompute
  14. 2026-10-11 01:48 UTCVendor advisory
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-10-10 13:07 UTCVendor advisory
  17. 2026-10-10 00:58 UTCEG score recompute
  18. 2026-10-10 00:58 UTCVendor advisory
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-10-09 12:51 UTCVendor advisory
  21. 2026-10-08 22:55 UTCEG score recompute
  22. 2026-10-08 22:55 UTCVendor advisory
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-10-08 10:48 UTCEG score recompute
  25. 2026-10-08 10:48 UTCVendor advisory
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  27. 2026-10-07 22:31 UTCVendor advisory
  28. 2026-10-07 10:23 UTCVendor advisory
  29. 2026-10-06 22:15 UTCEG score recompute
  30. 2026-10-06 22:15 UTCVendor advisory
  31. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  32. 2026-10-06 10:08 UTCVendor advisory
  33. 2026-10-05 21:44 UTCEG score recompute
  34. 2026-10-05 21:44 UTCVendor advisory
  35. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  36. 2026-10-05 09:21 UTCEG score recompute
  37. 2026-10-05 09:21 UTCVendor advisory
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  39. 2026-10-04 21:13 UTCVendor advisory
  40. 2026-10-04 09:04 UTCVendor advisory
  41. 2026-10-03 20:56 UTCEG score recompute
  42. 2026-10-03 20:56 UTCVendor advisory
  43. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-10-03 08:49 UTCVendor advisory
  45. 2026-10-02 20:40 UTCEG score recompute
  46. 2026-10-02 20:40 UTCVendor advisory
  47. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-10-02 08:15 UTCVendor advisory
  49. 2026-10-01 20:08 UTCEG score recompute
  50. 2026-10-01 20:08 UTCVendor advisory
  51. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  52. 2026-10-01 07:58 UTCVendor advisory
  53. 2026-09-30 19:51 UTCEG score recompute
  54. 2026-09-30 19:51 UTCVendor advisory
  55. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  56. 2026-09-30 07:44 UTCVendor advisory
  57. 2026-09-29 19:32 UTCEG score recompute
  58. 2026-09-29 19:32 UTCVendor advisory
  59. 2026-09-29 07:22 UTCEG score recompute
  60. 2026-09-29 07:22 UTCVendor advisory
  61. 2026-09-28 19:15 UTCEG score recompute
  62. 2026-09-28 19:15 UTCVendor advisory
  63. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  64. 2026-09-28 07:02 UTCVendor advisory
  65. 2026-09-27 18:51 UTCEG score recompute
  66. 2026-09-27 18:51 UTCVendor advisory
  67. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  68. 2026-09-27 06:44 UTCVendor advisory
  69. 2026-09-26 18:37 UTCEG score recompute
  70. 2026-09-26 18:37 UTCVendor advisory
  71. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  72. 2026-09-26 06:29 UTCEG score recompute
  73. 2026-09-26 06:29 UTCVendor advisory
  74. 2026-09-25 18:20 UTCVendor advisory
  75. 2026-09-25 06:07 UTCVendor advisory

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82412?
CVE-2026-82412 is a high-severity vulnerability; its CVE record was published on September 21, 2026. 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…
When was the CVE record for CVE-2026-82412 published?
The CVE record for CVE-2026-82412 was published on September 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-82412 actively exploited?
CVE-2026-82412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82412?
CVE-2026-82412 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82412?
A fix for CVE-2026-82412 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82412 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82412

Explore →

Is Your Infrastructure Affected by CVE-2026-82412?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs