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.
CVE-2026-38968
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-02. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- —
- EPSS
- 30.5%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 8, 2026
Advisory Details (2)
Auto-updated Jul 19, 2026commit 179a346ceb62 (ntop/ntopng)
Fix landed in ntop/ntopng commit 179a346ceb62 — awaiting tagged release
https://github.com/ntop/ntopng/commit/179a346ceb6239fd36128ccca3efa8f9ea61eeb5commit 14e22497233d (ntop/ntopng)
Fix landed in ntop/ntopng commit 14e22497233d — awaiting tagged release
https://github.com/ntop/ntopng/commit/14e22497233dc7d31d19dccb74b13bb073d16c2cVendor Advisories for CVE-2026-38968(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-38968Microsoft Security Response Center (MSRC)Critical
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.
- GHSA-5rrm-76q9-hp77GitHub Security AdvisoriesCritical
ntopng through 6.6 is vulnerable to Predictable Session Identifier which can lead to Session...
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 76× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 03:33 UTCGHSA enrichment
- 2026-07-16 23:35 UTCGHSA enrichment
- 2026-07-16 19:38 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 15:38 UTCGHSA enrichment
- 2026-07-16 11:32 UTCGHSA enrichment
- 2026-07-16 07:31 UTCGHSA enrichment
- 2026-07-16 03:33 UTCGHSA enrichment
- 2026-07-15 23:35 UTCGHSA enrichment
- 2026-07-15 19:37 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 15:40 UTCGHSA enrichment
- 2026-07-15 11:42 UTCGHSA enrichment
- 2026-07-15 07:36 UTCGHSA enrichment
- 2026-07-15 03:37 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 23:39 UTCGHSA enrichment
- 2026-07-14 19:41 UTCGHSA enrichment
- 2026-07-14 15:43 UTCGHSA enrichment
Show 51 moreShow fewer
- 2026-07-14 11:45 UTCGHSA enrichment
- 2026-07-14 07:48 UTCGHSA enrichment
- 2026-07-14 03:43 UTCGHSA enrichment
- 2026-07-13 23:45 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 19:47 UTCGHSA enrichment
- 2026-07-13 15:49 UTCGHSA enrichment
- 2026-07-13 11:51 UTCGHSA enrichment
- 2026-07-13 07:53 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 03:55 UTCGHSA enrichment
- 2026-07-12 23:57 UTCGHSA enrichment
- 2026-07-12 19:59 UTCGHSA enrichment
- 2026-07-12 16:00 UTCGHSA enrichment
- 2026-07-12 12:03 UTCGHSA enrichment
- 2026-07-12 08:04 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 04:06 UTCGHSA enrichment
- 2026-07-12 00:05 UTCGHSA enrichment
- 2026-07-11 20:07 UTCGHSA enrichment
- 2026-07-11 16:09 UTCGHSA enrichment
- 2026-07-11 12:11 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:13 UTCGHSA enrichment
- 2026-07-11 04:15 UTCGHSA enrichment
- 2026-07-11 00:17 UTCGHSA enrichment
- 2026-07-10 20:12 UTCGHSA enrichment
- 2026-07-10 16:15 UTCGHSA enrichment
- 2026-07-10 12:17 UTCGHSA enrichment
- 2026-07-10 08:20 UTCGHSA enrichment
- 2026-07-10 04:23 UTCGHSA enrichment
- 2026-07-10 00:23 UTCGHSA enrichment
- 2026-07-09 20:25 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 16:26 UTCGHSA enrichment
- 2026-07-09 12:26 UTCGHSA enrichment
- 2026-07-09 08:28 UTCEG score recompute▲ 9.80
- 2026-07-09 08:28 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 17:36 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 03:17 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-02 22:06 UTCEG score recompute
- 2026-07-02 22:06 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-38968?
When was CVE-2026-38968 disclosed?
Is CVE-2026-38968 actively exploited?
What is the CVSS score of CVE-2026-38968?
How do I remediate CVE-2026-38968?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-38968
Is Your Infrastructure Affected by CVE-2026-38968?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.