Quick answers
- Is CVE-2026-34017 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34017 being exploited in the wild.
- How severe is CVE-2026-34017?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Intel Hyperscan before 5.4.2.1.
- Is there a fix for CVE-2026-34017?
- Yes: fixed in Hyperscan 5.4.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34017 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-34017?
- 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: Hyperscan 5.4.2.1
Technical details
A heap-based buffer overflow vulnerability exists in Hyperscan's Ring 3 user application layer before v5.4.2.1. An unauthenticated, unprivileged local attacker with low attack complexity can trigger denial of service via malicious input; the attack requires passive user interaction and attack-triggering preconditions. The vulnerability impacts system availability with high severity and has low integrity impact.
Affected products
- Intel Hyperscan before 5.4.2.1
Timeline
- 2026-11-10: disclosed