BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-42586High confidence

Netty: CRLF Injection in Netty Redis Codec Encoder

netty · netty

Official source article: GitHub GHSA-RGRR-P7GP-5XJ7 ↗. Check the applicable product and release in the original source.

6.8MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs netty netty and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsnettyVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1:4.1.48-9ubuntu0.1+esm3Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenio.netty:netty-codec-redisECOSYSTEM: introduced 4.2.0.Alpha1; fixed 4.2.13.Final4.2.13.FinalOSV record ↗aggregator derived · 10 Sep 2026
Mavenio.netty:netty-codec-redisECOSYSTEM: introduced 0; fixed 4.1.133.Final4.1.133.FinalOSV record ↗aggregator derived · 10 Sep 2026
mavenio.netty:netty-codec-redis>= 4.2.0.Alpha1, <= 4.2.12.Final4.2.13.FinalGitHub advisory ↗upstream repository advisory · 11 Jun 2026
mavenio.netty:netty-codec-redis<= 4.1.132.Final4.1.133.FinalGitHub advisory ↗upstream repository advisory · 11 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-42586 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynetty-codec-redis: Netty: Command injection via CRLF characters in Redis codec encoder
3 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • netty-codec-redis as a component of Red Hat Fuse 7
  • netty-codec-redis as a component of Red Hat Process Automation 7
  • netty-codec-redis as a component of Red Hat Single Sign-On 7
Summary
A flaw was found in Netty, an asynchronous, event-driven network application framework. The Netty Redis codec encoder (RedisEncoder) does not properly validate or sanitize user-controlled string content for CRLF (Carriage Return Line Feed) characters. A remote attacker, by controlling the content of a Redis message, can inject arbitrary Redis commands or forge fake responses. This can lead to a high impact on data integrity.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-30129

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Improper Neutralization of CRLF Sequences ('CRLF Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-93 ↗

CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection'). The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-93Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1372Netty: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Netty ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260520Security Bulletin 20 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 20 May 2026, published on 20 May 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-42440 Référence CVE CVE-2026-42577 https://www.cve.org/CVERecord?id=CVE-2026-42577 Référence CVE CVE-2026-42578 https://www.cve.org/CVERecord?id=CVE-2026-42578 Référence CVE CVE-2026-42579 https://www.cve.org/CVERecord?id=CVE-2026-42579 Référence CVE CVE-2026-42580 https://www.cve.org/CVERecord?id=CVE-2026-42580 Référence CVE CVE-2026-42581 https://www.cve.org/CVERecord?id=CVE-2026-42581 Référence CVE CVE-2026-42583 https://www.cve.org/CVERecord?id=CVE-2026-42583 Référence CVE CVE-2026-42584 https://www.cve.org/CVERecord?id=CVE-2026-42584 Référence CVE CVE-2026-42585 https://www.cve.org/CVERecord?id=CVE-2026-42585 Référence CVE CVE-2026-42586 https://www.cve.org/CVERecord?id=CVE-2026-42586 Référence CVE CVE-2026-42587 https://www.cve.org/CVERecord?id=CVE-2026-42587 Référence CVE CVE-2026-43827 https://www.cve.org/CVERecord?id=CVE-2026-43827 Référence CVE CVE-2026-43828 https://www.cve.org/CVERecord?id=CVE-2026-43828 Référence CVE CVE-2026-43869 https://www.cve.org/CVERecord?id=CVE-2026-43869 Référence CVE CVE-2026-4410 https://www.cve.org/CVERecord?id=CVE-2026-4410 Référence CVE CVE-2026-44248 https://www.cve.org/CVERecord?id=CVE-2026-44248 Référence CVE CVE-2026-44249 https://www.cve.org/CVERecord?id=CVE-2026-44249 Référence CVE CVE-2026-44250 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-42403 Référence CVE CVE-2026-42404 https://www.cve.org/CVERecord?id=CVE-2026-42404 Référence CVE CVE-2026-42498 https://www.cve.org/CVERecord?id=CVE-2026-42498 Référence CVE CVE-2026-42577 https://www.cve.org/CVERecord?id=CVE-2026-42577 Référence CVE CVE-2026-42578 https://www.cve.org/CVERecord?id=CVE-2026-42578 Référence CVE CVE-2026-42580 https://www.cve.org/CVERecord?id=CVE-2026-42580 Référence CVE CVE-2026-42581 https://www.cve.org/CVERecord?id=CVE-2026-42581 Référence CVE CVE-2026-42584 https://www.cve.org/CVERecord?id=CVE-2026-42584 Référence CVE CVE-2026-42585 https://www.cve.org/CVERecord?id=CVE-2026-42585 Référence CVE CVE-2026-42586 https://www.cve.org/CVERecord?id=CVE-2026-42586 Référence CVE CVE-2026-42587 https://www.cve.org/CVERecord?id=CVE-2026-42587 Référence CVE CVE-2026-42778 https://www.cve.org/CVERecord?id=CVE-2026-42778 Référence CVE CVE-2026-42779 https://www.cve.org/CVERecord?id=CVE-2026-42779 Référence CVE CVE-2026-43512 https://www.cve.org/CVERecord?id=CVE-2026-43512 Référence CVE CVE-2026-43513 https://www.cve.org/CVERecord?id=CVE-2026-43513 Référence CVE CVE-2026-43514 https://www.cve.org/CVERecord?id=CVE-2026-43514 Référence CVE CVE-2026-43515 https://www.cve.org/CVERecord?id=CVE-2026-43515 Référence CVE CVE-2026-43827 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-016405NettyにおけるCRLF インジェクションの脆弱性

Nettyは非同期のイベント駆動型ネットワークアプリケーションフレームワークです。4.2.13.Finalおよび4.1.133.Finalより前のバージョンでは、NettyのRedisコーデックエンコーダ(RedisEncoder)がユーザー制御の文字列コンテンツを検証やサニタイズせずに直接ネットワーク出力バッファに書き込みます。Redisシリアル化プロトコル(RESP)はCRLF(\r\n)をコマンドおよびレスポンスの区切り文字として使用しているため、Redisメッセージの内容を制御できる攻撃者は任意のRedisコマンドを注入したり、偽のレスポンスを作成したりすることが可能です。この脆弱性は4.2.13.Finalおよび4.1.133.Finalで修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 13 May 2026 · Last source change 14 May 2026, 18:17 UTC · CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-30129
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 4.2.0.Alpha1, < 4.2.13.Final; < 4.1.133.Final · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 4.2.0.Alpha1, < 4.2.13.Final; < 4.1.133.Final · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    netty-codec-redis as a component of Red Hat Fuse 7; netty-codec-redis as a component of Red Hat JBoss Enterprise Application Platform 7; netty-codec-redis as a component of Red Hat Process Automation 7; netty-codec-redis as a component of Red Hat Single Sign-On 7 · Fixed: Red Hat Data Grid 8.6.2; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    After
    netty-codec-redis as a component of Red Hat Fuse 7; netty-codec-redis as a component of Red Hat Process Automation 7; netty-codec-redis as a component of Red Hat Single Sign-On 7 · Fixed: Red Hat Data Grid 8.6.2; Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-42586 · cve.blacktree.nl