Quick answers
- Is CVE-2026-38968 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38968 being exploited in the wild.
- How severe is CVE-2026-38968?
- Informational severity, with a CVSS score of 0, published 2 July 2026.
- Which products and versions are affected?
- Ntopng through 6.6.
- Is there a fix for CVE-2026-38968?
- A patch was published on 2026-07-02: Fixes committed to ntopng repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-38968 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-38968?
- 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.
Technical details
ntopng versions up to and including 6.6 utilize a weak pseudo-random number generator (PRNG) for creating HTTP session identifiers. Specifically, the implementation in src/HTTPserver.cpp relied on time-seeded 'srand' and 'rand' functions, which are not cryptographically secure. An attacker who can predict or control the timing of a login event may be able to determine the resulting session cookie, leading to session hijacking. The vulnerability has been addressed in recent commits by implementing a cryptographically strong random source (using BCrypt on Windows and improved entropy sources on other platforms) and incorporating additional variables like packet counts and usernames into the session generation logic.
Affected products
- ntop ntopng through 6.6
Timeline
- 2026-07-02: advisory: CVE-2026-38968 published by NVD
- 2026-07-02: patched: Fixes committed to ntopng repository