Quick answers
- Is CVE-2026-40216 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40216 being exploited in the wild.
- How severe is CVE-2026-40216?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Intel Hyperscan before v5.4.2.1.
- Is there a fix for CVE-2026-40216?
- Yes: fixed in v5.4.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40216 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-40216?
- Check whether you run Intel Hyperscan 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.
How to fix
- Fixed in: v5.4.2.1
Technical details
Seven distinct vulnerabilities affect Hyperscan before v5.4.2.1 in user-mode applications, including untrusted pointer dereference (CVE-2026-34489), out-of-bounds write (CVE-2026-33094, CVE-2026-40694), null pointer dereference (CVE-2028-28730), heap-based buffer overflow (CVE-2026-34017, CVE-2026-63540), and out-of-bounds read (CVE-2026-40424, CVE-2026-40216). Attack vectors are local with low complexity; most require no authentication and no user interaction. Exploitation results in availability impact (high on most), with some variants affecting integrity or confidentiality (low).
Affected products
- Intel Hyperscan before v5.4.2.1
Timeline
- 2026-11-10: disclosed