CVE-2026-63540 · Package
NO FIX YET · SEE WHAT TO DO
Hyperscan, Intel's regular-expression matching library, has a heap-based buffer overflow before version v5.4.2.1 that an unprivileged local user can trigger. An attacker can cause a denial of service, and the description also notes possible integrity impact.
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 running Hyperscan in Ring 3 user space that pass data through its matching engine are the ones exposed. Systems that do not use Hyperscan are not affected. The sources do not say which configurations or inputs are needed beyond local access.
Not affected if hyperscan-not-installed, version-at-or-above-5.4.2.1
Who cares c, hyperscan, regex
v5.4.2.1v5.4.2.1 or laterHeap-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 not 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:N/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.