CVE-2019-9169
In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attemp
CVSS
9.8
Critical
EPSS
4.7%
p92
KEV
—
Exploit Today
28
0-100
Published: Feb 26, 2019 · Last modified: Oct 14, 2026 · CWE-125
4.7%EPSS · 30 days4.7%
2026-10-172026-11-13
In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.
- www.securityfocus.comhttp://www.securityfocus.com/bid/107160
- debbugs.gnu.orghttps://debbugs.gnu.org/cgi/bugreport.cgi?bug=34140
- debbugs.gnu.orghttps://debbugs.gnu.org/cgi/bugreport.cgi?bug=34142
- kc.mcafee.comhttps://kc.mcafee.com/corporate/index?page=content&id=SB10278
- security.gentoo.orghttps://security.gentoo.org/glsa/202006-04
- security.netapp.comhttps://security.netapp.com/advisory/ntap-20190315-0002/
- sourceware.orghttps://sourceware.org/bugzilla/show_bug.cgi?id=24114
- sourceware.orghttps://sourceware.org/git/gitweb.cgi?p=glibc.git%3Ba=commit%3Bh=583dd860d5b833037175247230a328f0050dbfe9
- support.f5.comhttps://support.f5.com/csp/article/K54823184
- usn.ubuntu.comhttps://usn.ubuntu.com/4416-1/
- www.oracle.comhttps://www.oracle.com/security-alerts/cpuapr2022.html
- www.securityfocus.comhttp://www.securityfocus.com/bid/107160
- debbugs.gnu.orghttps://debbugs.gnu.org/cgi/bugreport.cgi?bug=34140
- debbugs.gnu.orghttps://debbugs.gnu.org/cgi/bugreport.cgi?bug=34142
- kc.mcafee.comhttps://kc.mcafee.com/corporate/index?page=content&id=SB10278
- security.gentoo.orghttps://security.gentoo.org/glsa/202006-04
- security.netapp.comhttps://security.netapp.com/advisory/ntap-20190315-0002/
- sourceware.orghttps://sourceware.org/bugzilla/show_bug.cgi?id=24114
- sourceware.orghttps://sourceware.org/git/gitweb.cgi?p=glibc.git%3Ba=commit%3Bh=583dd860d5b833037175247230a328f0050dbfe9
- support.f5.comhttps://support.f5.com/csp/article/K54823184
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1294326.5 MED—
———Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_mountd() in src/dissectors/ec_mountd.c that validates RPC credential and directory lengths independently rather than against the packet end. Network-adjacent attackers can send a crafted MOUNT MNT call to read up to 100 bytes past the heap buffer, leaking memory to the console and logs.20hCVE-2026-1294316.5 MED—
———Ettercap through 0.8.5.1 contains a heap out-of-bounds read vulnerability in dissector_socks() in src/dissectors/ec_socks.c that allows network-adjacent attackers to read heap memory via unchecked SOCKS5 username/password lengths. Attackers can send a crafted SOCKS5 authentication packet observed by Ettercap to read up to 255 bytes past the heap buffer, disclosing memory printed and logged as captured credentials.20hCVE-2026-646755.3 MED—
——0BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5 and 1.5.1, a single unauthenticated BACnet/IP UDP datagram (port 47808) triggers an out-of-bounds read in xy_color_decode() (src/bacnet/lighting.c), reachable pre-authentication through two default-registered service handlers: the UnconfirmedRequest WriteGroup service (0x0A) and Confirmed WriteProperty on a BACnetXYColor-typed property. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.1dCVE-2026-62976——
——0BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the RAMFS-backed FILE object implementation stores appended records as NUL-terminated strings, but its record-counting logic later walks the buffer as if an additional terminating empty record were present. As a result, two consecutive AtomicWriteFile(record-access) append requests can cause record_count() to call bacnet_strnlen() on a pointer that is already one byte past the end of the heap allocation. This issue has been patched in versions 1.5.1 and 1.6.0.1dCVE-2026-62975——
——0BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the RAMFS-backed FILE implementation accepts AtomicWriteFile(record-access) requests that replace existing records with caller-controlled content. If a client replaces a record with shorter data, the backend can shrink the heap allocation and then continue processing with a trailing-copy length derived from the old layout. During that replace path, the RAMFS backend computes the trailing-copy length from the old file layout, then shrinks the heap allocation, and finally uses the stale length in memmove(). As a result, the source range of that memmove() can extend beyond the end of the reallocated heap buffer, producing a heap out-of-bounds read. This issue has been patched in versions 1.5.1 and 1.6.0.1dCVE-2026-129217——
——0In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end of a heap buffer and the 16-bit length of the encapsulated data underflows to 65535, causing a 65535-byte out-of-bounds heap read followed by an assertion failure. A remote BGP peer that has established a session and negotiated the Graceful Restart capability with the Notification (N) bit can send such a message to crash the bgpd daemon, terminating all BGP sessions (denial of service). This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0.2d