CyberSecBulletin

Null Byte Interaction Error (Poison Null Byte)

CWE-626

The product does not properly handle null bytes or NUL characters when passing data between different representations or components.

A null byte (NUL character) can have different meanings across representations or languages. For example, it is a string terminator in standard C libraries, but Perl and PHP strings do not treat it as a terminator. When two representations are crossed - such as when Perl or PHP invokes underlying C functionality - this can produce an interaction error with unexpected results. Similar issues have been reported for ASP. Other interpreters written in C might also be affected. The poison null byte is frequently useful in path traversal attacks by terminating hard-coded extensions that are added to a filename. It can play a role in regular expression processing in PHP.

We track 3 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.8.

How this weakness is prevented

  • Implementation: Remove null bytes from all incoming strings.

Latest Null Byte Interaction Error (Poison Null Byte) vulnerabilities

  • 7.5 High severity

    netty: Null Byte Interaction Error (Poison Null Byte)

    CVE-2026-62380Netty

    Netty (io.netty:netty-codec-socks) versions 4.2.0.Final through 4.2.16.Final and 4.1.x through 4.1.136.Final contain null byte, CRLF, and credential injection vulnerabilities in the SOCKS4 (Socks4ClientEncoder) and SOCKS5 (Socks5ClientEncoder) client encoders,

  • 9.1 Critical severity

    Netty is an asynchronous, event-driven network application framework.

    CVE-2026-42579NettyEPSS 1.01%

    Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty's DNS codec does not enforce RFC 1035 domain name constraints during either encoding or decoding. This creates a bidirectional attack surface:

  • 9.8 Critical severity

    Red Hat Enterprise Linux 10: Improper Null Termination

    CVE-2026-42010Red HatEPSS 1.05%

    A flaw was found in gnutls. Servers configured with RSA-PSK (Rivest–Shamir–Adleman – Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username,