CVE-2026-34017 · Package
NO FIX YET · SEE WHAT TO DO
Hyperscan, Intel's regular expression matching library, has a heap-based buffer overflow in versions before v5.4.2.1. A local, unprivileged user can trigger it to cause a denial of service.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that build or ship software linking Hyperscan for pattern matching, especially where untrusted local users can reach the matching path. The sources do not say which products or configurations use it in a way that exposes them. Systems that do not include Hyperscan are not affected.
Not affected if hyperscan-not-used, hyperscan-v5.4.2.1-or-later
Who cares c++, hyperscan
pkg-config --modversion libhs or the version in your build files.v5.4.2.1 or later.Heap-based buffer overflow for some Hyperscan before version v5.4.2.1 within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires passive user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.