Regcomp and Regexec Functions
Source GCVE Database
Not known to be exploited · CVSS 3.7 Low.
Data as of 11 Nov 2026, 20:03 UTC
Thin evidence
One scorer or none| CNA (glibc) | CVSS 3.1 | 3.7 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| The GNU C Libraryglibc | Affected
| Fixed in– |
AI-suggested
Until a fix is available, mitigating memory pressure on affected systems may reduce the likelihood of triggering the issue.
Description
A vulnerability in GNU C Library versions 2.3 through 2.44 affects the regcomp and regexec functions, which may read freed memory and double-free heap blocks when memory allocation fails during regular expression compilation or matching. This can cause process crashes under memory pressure conditions. The issue does not require crafted regular expressions and affects all architectures supported by the library.