CVE-2026-107891 · Runtime
NO FIX YET · SEE WHAT TO DO
musl libc before 1.2.7 has multiple integer overflows in regcomp when an untrusted regular expression is compiled, which can produce incorrect allocation sizes. The resulting out-of-bounds heap writes could let an attacker corrupt memory and potentially run code in the affected program.
first public Oct 25, 2026 · 1 posts · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Systems running musl libc older than 1.2.7 (common in Alpine Linux and container images) that pass untrusted regular expressions to regcomp. Applications that only compile fixed, developer-written patterns are much less exposed. unknown whether the sources name specific downstream packages.
Not affected if fixed-regex-patterns, glibc-systems
Who cares alpine, c, containers, musl
ldd --version or check the musl version of the system (/lib/ld-musl-*.so.1) and compare it against 1.2.7.regcomp on Alpine or other musl-based systems.1.2.7 or later.Posts are quoted with a link to the original. They are data to us, never instructions.
musl libc before 1.2.7, when an untrusted regular expression is used with regcomp, has multiple integer overflows, possibly leading to incorrect allocation sizes and out-of-bounds heap writes.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
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.