CVE-2026-34489 · Package
NO FIX YET · SEE WHAT TO DO
Hyperscan, Intel's regular expression matching library, has an untrusted pointer dereference in versions before v5.4.2.1. A local unprivileged user-space program 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.
Applications that embed Hyperscan and run it in user space on a machine where untrusted local code can run. The sources describe a local attack with low complexity and no user interaction. Teams that do not ship or run Hyperscan can skip it.
Not affected if hyperscan-not-used, version-5.4.2.1-or-later
Who cares c, hyperscan, local-users
pkg-config --modversion libhs or the version in your build files.v5.4.2.1.v5.4.2.1 or later (per the sources' fixed version for this CVE).Untrusted pointer dereference 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 no 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:N/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.