ntopng: Stack buffer overflow (write) in nDPI custom category detection allows remote code execution via crafted network packets
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 6.7.260721
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.7.260721.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 40/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
ntopng, a web-based network traffic monitoring application, has a stack buffer overflow in its nDPI custom category detection that lets an attacker corrupt the stack and cause a denial of service. An attacker can reach it remotely over the network without logging in or any user action, by sending packets that match custom-category rules.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
ntopng is a web-based network traffic monitoring application. Prior to 6.7.260721, ndpi_get_custom_category_match writes a four-byte nDPI protocol-category value through a pointer to the two-byte id variable in IpAddress::reloadBlacklist in src/IpAddress.cpp during packet dissection and host initialization. A remote unauthenticated attacker on a monitored network segment can send packets that match custom-category rules, causing stack corruption and denial of service without user interaction. This issue is fixed in version 6.7.260721.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.7.260721.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- ntop ntopng
fixed in 6.7.260721
Evidence 2
- Advisory
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97371
Is CVE-2026-97371 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-97371?
ntopng: before 6.7.260721.Source: cve.now feed data
How do I fix CVE-2026-97371?
Upgrade to a fixed version: 6.7.260721.Source: cve.now feed data