https://seclists.org/oss-sec/2026/q1/349: Off-by-one heap buffer overflow in libuv
Published Mar 19, 2026
·Updated
Affected Software
1 affected component
libuv libuv>=1.47.0
Frequently Asked Questions
1
What is the severity of CVE-2026-XXXX?
The severity of CVE-2026-XXXX is expected to be high due to the nature of the off-by-one heap buffer overflow vulnerability.
2
How do I fix CVE-2026-XXXX?
To fix CVE-2026-XXXX, update to the patched version of libuv that addresses the heap buffer overflow.
3
What versions of libuv are affected by CVE-2026-XXXX?
CVE-2026-XXXX affects all versions of libuv prior to the release that includes the fix.
4
What is an off-by-one heap buffer overflow in the context of CVE-2026-XXXX?
An off-by-one heap buffer overflow occurs when a program writes just beyond the end of a buffer, potentially corrupting adjacent memory.
5
Is CVE-2026-XXXX exploitable?
CVE-2026-XXXX is not directly exploitable as per the current reported Proof of Concept; however, it could be leveraged under certain conditions.