Cyber Resilience

CVE-2026-42586

Netty ≤ 4.1.133

Public PoC
Published
13 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 6.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS Score 0.0020 10th percentile
Risk Priority 37 floored blend · peak EPSS

Summary

CVE-2026-42586 is a medium-severity CRLF Injection (CWE-93) vulnerability in Netty Netty. Its CVSS base score is 6.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
Why these techniques?

CRLF injection in Redis codec enables arbitrary command injection (T1059) against Redis via exploitation of public-facing Netty-based apps (T1190).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-67735Same product: Netty Netty
CVE-2026-41417Same product: Netty Netty
CVE-2026-50020Same product: Netty Netty
CVE-2026-42581Same product: Netty Netty
CVE-2026-42585Same product: Netty Netty
CVE-2026-42580Same product: Netty Netty
CVE-2025-58056Same product: Netty Netty
CVE-2026-33870Same product: Netty Netty
CVE-2026-42579Same product: Netty Netty
CVE-2026-42578Same product: Netty Netty

Affected Assets

netty
netty
≤ 4.1.133 · 4.2.0 — 4.2.13

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-15 Information Output Filtering
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.2.4

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation and sanitization of untrusted string inputs before they are written into the Redis RESP protocol stream, blocking CRLF injection.

prevent

Requires filtering of information outputs to ensure only intended protocol content is emitted by the RedisEncoder, mitigating unsanitized user data.

prevent

Enforces information-flow rules on the Redis codec so that only well-formed RESP messages (no embedded delimiters) are allowed to traverse the network channel.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and validation to block CRLF injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect CRLF flaws but does not itself implement the neutralization.

prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection.

prevents

Application security requirements include rules for neutralizing special characters such as CRLF in inputs.

prevents

Secure architecture principles encourage safe handling of untrusted data but do not prescribe specific CRLF controls.

prevents

Secure coding standards explicitly require neutralization of CRLF sequences, fully addressing this weakness.

References