# CVE-2026-38968: Weak cryptography in n/a

> Attackers can hijack sessions in ntopng by predicting weak time-seeded session identifiers, leading to unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** AZL-92103, GHSA-5rrm-76q9-hp77, UBUNTU-CVE-2026-38968

## What is CVE-2026-38968?

CVE-2026-38968 is a critical vulnerability in n/a, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-341 (Predictable from Observable State)

## Which versions are affected by CVE-2026-38968?

It affects 1 product.


Products: Ntop Ntopng.

## How do I fix CVE-2026-38968?

No fix has been published for CVE-2026-38968 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-38968 being exploited?

There is no known exploitation of CVE-2026-38968 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-5473](https://insights.sbomify.com/CVE-2017-5473/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-12520](https://insights.sbomify.com/CVE-2018-12520/): Weak cryptography in n/a (high 8.1)
- [CVE-2017-7458](https://insights.sbomify.com/CVE-2017-7458/): Null dereference in n/a (high 7.5)
- [CVE-2017-7459](https://insights.sbomify.com/CVE-2017-7459/): Other in n/a (high 7.5)
- [CVE-2017-7416](https://insights.sbomify.com/CVE-2017-7416/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-38968 and fix it if it is affected.

What it is: CVE-2026-38968 is a critical vulnerability in n/a, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38968 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-38968/ (Markdown: https://insights.sbomify.com/CVE-2026-38968/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-38968
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-38968
- OSV: https://osv.dev/vulnerability/CVE-2026-38968

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-38968/
Summaries are generated and may contain mistakes; the official description above is the record.