Quick answers
- Is CVE-2026-97371 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97371 being exploited in the wild.
- How severe is CVE-2026-97371?
- Medium severity, with a CVSS score of 5.3, published 5 November 2026.
- Which products and versions are affected?
- Ntopng prior to 6.7.260721.
- Is there a fix for CVE-2026-97371?
- Yes: fixed in 6.7.260721. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-97371 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-97371?
- Check whether you run Ntopng at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.7.260721
Technical details
The ndpi_get_custom_category_match function performs a 4-byte write to a 2-byte stack variable (id) in IpAddress::reloadBlacklist during packet dissection and host initialization, causing stack corruption. The vulnerability is network-triggered with no authentication required and occurs in the normal packet processing path. A remote attacker on the monitored network segment can send crafted packets to trigger stack overflow, leading to denial of service or potential code execution.
Affected products
- ntop ntopng prior to 6.7.260721
Timeline
- 2026-07-21: disclosed
- 2026-07-21: patched