Bug 2477213 (CVE-2026-42586) - CVE-2026-42586 netty-codec-redis: Netty: Command injection via CRLF characters in Redis codec encoder
Summary: CVE-2026-42586 netty-codec-redis: Netty: Command injection via CRLF character...
Keywords:
Status: NEW
Alias: CVE-2026-42586
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-13 19:01 UTC by OSIDB Bzimport
Modified: 2026-07-20 11:59 UTC (History)
43 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:37390 0 None None None 2026-07-09 15:31:00 UTC
Red Hat Product Errata RHSA-2026:41951 0 None None None 2026-07-20 11:59:48 UTC

Description OSIDB Bzimport 2026-05-13 19:01:29 UTC 
Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, the Netty Redis codec encoder (RedisEncoder) writes user-controlled string content directly to the network output buffer without validating or sanitizing CRLF (\r\n) characters. Since the Redis Serialization Protocol (RESP) uses CRLF as the command/response delimiter, an attacker who can control the content of a Redis message can inject arbitrary Redis commands or forge fake responses. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.
Comment 3 errata-xmlrpc 2026-07-09 15:30:57 UTC 
This issue has been addressed in the following products:

  Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16

Via RHSA-2026:37390 https://access.redhat.com/errata/RHSA-2026:37390
Comment 4 errata-xmlrpc 2026-07-20 11:59:45 UTC 
This issue has been addressed in the following products:

  Red Hat Data Grid 8.6.2

Via RHSA-2026:41951 https://access.redhat.com/errata/RHSA-2026:41951
Note You need to log in before you can comment on or make changes to this bug.