CVE-2026-38968 ntopng Vulnerability
ntopng through 6.6 is vulnerable to Predictable Session Identifier which can lead to Session Hijacking. HTTP session identifiers in src/HTTPserver.cpp use weak time-seeded pseudo-randomness during session creation. As a result, fresh authenticated logins can receive deterministic or colliding session cookies under attacker-controlled timing.
Quick answer
ntopng should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- ntopng through 6.6
Fixed versions
- ntopng build containing commits 14e2249 and 179a346 or later
How to fix it
CVE-2026-38968 affects ntopng. The affected range is ntopng through 6.6. Update to ntopng build containing commits 14e2249 and 179a346 or later. Fix exposed systems first, especially where internet-facing services, admin panels, and trusted internal users can be reached. If abuse is suspected, review logs and rotate secrets that may have been exposed.
- Inventory every ntopng install and note the exact version.
- Compare each install with the affected range: ntopng through 6.6.
- Update to ntopng build containing commits 14e2249 and 179a346 or later.
- If you cannot patch today, restrict internet-facing services, admin panels, and trusted internal users to trusted users and networks.
- Back up the current configuration before changing production systems.
- Review recent logs for crashes, strange admin actions, failed logins, or unexpected access.
- Rotate passwords, tokens, certificates, or keys if compromise is suspected.
- Document the change, owner, date, and final version.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version now matches the fixed guidance: ntopng build containing commits 14e2249 and 179a346 or later.
- Confirm old affected versions are no longer deployed: ntopng through 6.6.
- Confirm internet-facing services, admin panels, and trusted internal users is limited to the smallest needed group.
- Rerun the relevant Fixnx scan or internal security check after the change.
- Save logs, screenshots, or package output as proof of the fix.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-38968?
ntopng versions listed as affected should be reviewed: ntopng through 6.6.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.