Cyber Resilience

CVE-2026-38968

Ntopng ≤ 6.6

Published
02 July 2026
Modified
08 July 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0038 31th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2026-38968 is a critical-severity Predictable from Observable State (CWE-341) vulnerability in Ntop Ntopng. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

EU & UK References

No EU or UK CSIRT advisories indexed for this CVE.

Vulnerability Data

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…

more

under attacker-controlled timing.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
T1563 Remote Service Session Hijacking Lateral Movement
Adversaries may take control of preexisting sessions with remote services to move laterally in an environment.
T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-42365Shared CWE-341
CVE-2025-40780Shared CWE-341
CVE-2025-48461Shared CWE-341
CVE-2025-42925Shared CWE-341
CVE-2024-10141Shared CWE-341
CVE-2025-25066Same vendor: Ntop
CVE-2026-36609Shared CWE-341
CVE-2023-49259Shared CWE-341
CVE-2026-5081Shared CWE-341
CVE-2026-40164Shared CWE-341

Affected Assets

ntop
ntopng
≤ 6.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.6.1
  • V6.5.1
  • V6.5.3
  • V6.5.5

Mitigating Controls (NIST 800-53 r5) AI

Authenticator management requires generation and distribution of values that cannot be derived from observable state.

Cryptographic key establishment mandates use of unpredictable, non-observable values for keys and nonces.

Session authenticity protection requires session identifiers or tokens that resist prediction from network or timing observations.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require cryptographically secure random values instead of observable state such as time or PID.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce use of cryptographically secure RNG sources and disable predictable state-based mechanisms.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Cryptographic controls replace predictable values with high-entropy, non-guessable material.

finds

Security testing can detect predictability issues but does not prevent them by itself.

prevents

SDLC requirements encourage secure design but do not directly mandate removal of predictable state.

prevents

Secure coding practices explicitly forbid use of predictable state (time, PID, counters) for secrets or tokens.

prevents

Strong authentication mechanisms reduce reliance on predictable state-derived tokens or identifiers.

none

Accurate time sources limit one observable state vector but do not address broader predictability.

References