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

Netty HTTP/2: Advertised MAX_CONCURRENT_STREAMS are not enforced

netty · netty

Official source article: GitHub GHSA-5X3R-WRVG-RP6Q ↗. Check the applicable product and release in the original source.

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.51% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

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-appsnettyUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical 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-http2ECOSYSTEM: introduced 4.2.0.Final; fixed 4.2.15.Final4.2.15.FinalOSV record ↗aggregator derived · 10 Sep 2026
Mavenio.netty:netty-codec-http2ECOSYSTEM: introduced 0; fixed 4.1.135.Final4.1.135.FinalOSV record ↗aggregator derived · 10 Sep 2026
mavenio.netty:netty-codec-http2>= 4.2.0.Final, <= 4.2.14.Final4.2.15.FinalGitHub advisory ↗upstream repository advisory · 12 Jun 2026
mavenio.netty:netty-codec-http2<= 4.1.134.Final4.1.135.FinalGitHub advisory ↗upstream repository advisory · 12 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-47244 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynetty-codec-http2: Netty: Denial of Service via uncontrolled HTTP/2 concurrent streams
42 known affected

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

  • netty-codec-http2 as a component of Cryostat 4
  • openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9 as a component of OpenShift Serverless
  • netty-codec-http2 as a component of Red Hat AMQ Broker 7
Summary
A flaw was found in Netty, a network application framework. A remote attacker can exploit this vulnerability by sending a large number of HTTP/2 stream requests to a Netty HTTP/2 server. If the server does not explicitly limit concurrent streams, it can lead to the allocation of numerous long-lived stream objects. This excessive resource consumption can result in a denial of service (DoS), making the server unavailable to legitimate users.
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-36455

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 no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAX_VALUE, and Http2Settings never inserts SETTINGS_MAX_CONCURRENT_STREAMS by default (Http2Settings.java:305-307 only clamps a user-supplied value). Unless the application explicitly calls initialSettings().maxConcurrentStreams(n), a Netty HTTP/2 server advertises no limit and enforces none locally. Each open stream allocates a DefaultStream object, PropertyMap slots, flow-controller state and IntObjectHashMap entry; with ~2^30 permissible odd stream IDs a single TCP connection can create hundreds of thousands of long-lived stream objects. This is also the precondition for CVE-2023-44487-style Rapid-Reset amplification, where the absence of a low concurrent cap multiplies backend work. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

What

Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAX_VALUE, and Http2Settings never inserts SETTINGS_MAX_CONCURRENT_STREAMS by default (Http2Settings.java:305-307 only clamps a user-supplied value). Unless the application explicitly calls initialSettings().maxConcurrentStreams(n), a Netty HTTP/2 server advertises no limit and enforces none locally. Each open stream allocates a DefaultStream object, PropertyMap slots, flow-controller state and IntObjectHashMap entry; with ~2^30 permissible odd stream IDs a single TCP connection can create hundreds of thousands of long-lived stream objects. This is also the precondition for CVE-2023-44487-style Rapid-Reset amplification, where the absence of a low concurrent cap multiplies backend work. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path 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 a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, DefaultHttp2Connection.DefaultEndpoint initialises maxActiveStreams/maxStreams to Integer.MAX_VALUE, and Http2Settings never inserts SETTINGS_MAX_CONCURRENT_STREAMS by default (Http2Settings.java:305-307 only clamps a user-supplied value). Unless the application explicitly calls initialSettings().maxConcurrentStreams(n), a Netty HTTP/2 server advertises no limit and enforces none locally. Each open stream allocates a DefaultStream object, PropertyMap slots, flow-controller state and IntObjectHashMap entry; with ~2^30 permissible odd stream IDs a single TCP connection can create hundreds of thousands of long-lived stream objects. This is also the precondition for CVE-2023-44487-style Rapid-Reset amplification, where the absence of a low concurrent cap multiplies backend work. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path 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.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Uncontrolled Resource Consumption → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
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-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-400
A

Official authority intelligence

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

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

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Netty ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-3047IBM Planning Analytics: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Planning Analytics ausnutzen, um einen Denial of Service Angriff durchzuführen oder Daten zu manipulieren.

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

d?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=CVE-2026-47059 Référence CVE CVE-2026-47063 https://www.cve.org/CVERecord?id=CVE-2026-47063 Référence CVE CVE-2026-47065 https://www.cve.org/CVERecord?id=CVE-2026-47065 Référence CVE CVE-2026-47244 https://www.cve.org/CVERecord?id=CVE-2026-47244 Référence CVE CVE-2026-47838 https://www.cve.org/CVERecord?id=CVE-2026-47838 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-48006 https://www.cve.org/CVERecord?id=CVE-2026-48006 Référence CVE CVE-2026-48043 https://www.cve.org/CVERecord?id=CVE-2026-48043 Référence CVE CVE-2026-48059 https://www.cve.org/CVERecord?id=CVE-2026-48059 Référence CVE CVE-2026-48155 https://www.cve.org/CVERecord?id=CVE-2026-48155 Référence CVE CVE-2026-48156 https://www.cve.org/CVERecord?id=CVE-2026-48156 Référence CVE CVE-2026-4867 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=CVE-2026-47059 Référence CVE CVE-2026-47063 https://www.cve.org/CVERecord?id=CVE-2026-47063 Référence CVE CVE-2026-47065 https://www.cve.org/CVERecord?id=CVE-2026-47065 Référence CVE CVE-2026-47244 https://www.cve.org/CVERecord?id=CVE-2026-47244 Référence CVE CVE-2026-47834 https://www.cve.org/CVERecord?id=CVE-2026-47834 Référence CVE CVE-2026-47838 https://www.cve.org/CVERecord?id=CVE-2026-47838 Référence CVE CVE-2026-47841 https://www.cve.org/CVERecord?id=CVE-2026-47841 Référence CVE CVE-2026-47842 https://www.cve.org/CVERecord?id=CVE-2026-47842 Référence CVE CVE-2026-47877 https://www.cve.org/CVERecord?id=CVE-2026-47877 Référence CVE CVE-2026-47883 https://www.cve.org/CVERecord?id=CVE-2026-47883 Référence CVE CVE-2026-47884 https://www.cve.org/CVERecord?id=CVE-2026-47884 Référence CVE CVE-2026-47885 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-44248 Référence CVE CVE-2026-46968 https://www.cve.org/CVERecord?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=CVE-2026-47059 Référence CVE CVE-2026-47063 https://www.cve.org/CVERecord?id=CVE-2026-47063 Référence CVE CVE-2026-47244 https://www.cve.org/CVERecord?id=CVE-2026-47244 Référence CVE CVE-2026-48043 https://www.cve.org/CVERecord?id=CVE-2026-48043 Référence CVE CVE-2026-48959 https://www.cve.org/CVERecord?id=CVE-2026-48959 Référence CVE CVE-2026-48962 https://www.cve.org/CVERecord?id=CVE-2026-48962 Référence CVE CVE-2026-50560 https://www.cve.org/CVERecord?id=CVE-2026-50560 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-54225 https://www.cve.org/CVERecord?id=CVE-2026-54225 Référence CVE CVE-2026-57819 https://www.cve.org/CVERecord?id=CVE-2026-57819 Référence CVE CVE-2026-59879 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45416 Référence CVE CVE-2026-46968 https://www.cve.org/CVERecord?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=CVE-2026-47059 Référence CVE CVE-2026-47063 https://www.cve.org/CVERecord?id=CVE-2026-47063 Référence CVE CVE-2026-47244 https://www.cve.org/CVERecord?id=CVE-2026-47244 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-48043 https://www.cve.org/CVERecord?id=CVE-2026-48043 Référence CVE CVE-2026-50020 https://www.cve.org/CVERecord?id=CVE-2026-50020 Référence CVE CVE-2026-50560 https://www.cve.org/CVERecord?id=CVE-2026-50560 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-54225 https://www.cve.org/CVERecord?id=CVE-2026-54225 Référence CVE CVE-2026-5516 https://www.cve.org/CVERecord?id=CVE-2026-5516 Référence CVE CVE-2026-5588 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019793Nettyにおけるリソースの枯渇に関する脆弱性

Nettyは、プロトコルサーバーおよびクライアントの開発のためのネットワークアプリケーションフレームワークです。バージョン4.1.135.Finalおよび4.2.15.Final以前では、DefaultHttp2Connection.DefaultEndpointはmaxActiveStreams/maxStreamsをInteger.MAX_VALUEに初期化し、Http2SettingsはデフォルトでSETTINGS_MAX_CONCURRENT_STREAMSを挿入しません（Http2Settings.javaの305から307行ではユーザー提供値のみを制限します）。アプリケーションが明示的にinitialSettings().maxConcurrentStreams(n)を呼び出さない限り、NettyのHTTP/2サーバーは制限を広告せず、ローカルでも制限を強制しません。各オープンストリームはDefaultStreamオブジェクト、PropertyMapスロット、フローコントローラー状態、およびIntObjectHashMapエントリを割り当てます。約2の30乗の許容される奇数ストリームIDにより、単一のTCP接続で数十万もの長期間維持されるストリームオブジェクトを作成できます。これは、低い同時接続上限がないことでバックエンドの負荷を増幅するRapid-Reset増幅の前提条件となっています。バージョン4.1.135.Finalおよび4.2.15.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
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 12 Jun 2026 · Last source change 12 Jun 2026, 14:59 UTC · CWE-400 · Uncontrolled Resource Consumption

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-36455
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.Final, < 4.2.15.Final; < 4.1.135.Final · Fixed: Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    After
    >= 4.2.0.Final, < 4.2.15.Final; < 4.1.135.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. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-47244 to remediation: access.redhat.com/CVE-2026-47244.
    Before
    remediation: access.redhat.com/CVE-2026-47244
    After
    remediation: access.redhat.com/CVE-2026-47244
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    netty-codec-http2 as a component of Cryostat 4; openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9 as a component of OpenShift Serverless; netty-codec-http2 as a component of Red Hat AMQ Broker 7; netty-codec-http2 as a component of Red Hat build of Apache Camel - HawtIO 4; netty-codec-http2 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; netty-codec-http2 as a component of Red Hat build of Apache Camel for Spring Boot 4; netty-codec-http2 as a component of Red Hat build of Apicurio Registry 3; netty-codec-http2 as a component of Red Hat build of Debezium 3; netty-codec-http2 as a component of Red Hat Build of Keycloak; rhbk-openshift-rhel9/rhbk-openshift-rhel9 as a component of Red Hat Build of Keycloak; rhbk-rhel9-operator/rhbk-rhel9-operator as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9-operator as a component of Red Hat Build of Keycloak; netty-codec-http2 as a component of Red Hat Data Grid 8; netty-codec-http2 as a component of Red Hat Fuse 7; netty-codec-http2 as a component of Red Hat JBoss Enterprise Application Platform 7; netty-codec-http2 as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; rhoai/odh-modelmesh-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-openvino-model-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-spark-operator-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); and 12 more · Fixed: Red Hat JBoss Enterprise Application Platform 8.1; Red Hat build of Quarkus 3.27.4.SP1; Red Hat build of Quarkus 3.33.2.SP1
    After
    netty-codec-http2 as a component of Cryostat 4; openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9 as a component of OpenShift Serverless; netty-codec-http2 as a component of Red Hat AMQ Broker 7; netty-codec-http2 as a component of Red Hat build of Apache Camel - HawtIO 4; netty-codec-http2 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; netty-codec-http2 as a component of Red Hat build of Apache Camel for Spring Boot 4; netty-codec-http2 as a component of Red Hat build of Apicurio Registry 3; netty-codec-http2 as a component of Red Hat build of Debezium 3; netty-codec-http2 as a component of Red Hat Build of Keycloak; rhbk-openshift-rhel9/rhbk-openshift-rhel9 as a component of Red Hat Build of Keycloak; rhbk-rhel9-operator/rhbk-rhel9-operator as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9-operator as a component of Red Hat Build of Keycloak; netty-codec-http2 as a component of Red Hat Data Grid 8; netty-codec-http2 as a component of Red Hat Fuse 7; netty-codec-http2 as a component of Red Hat JBoss Enterprise Application Platform 7; netty-codec-http2 as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; rhoai/odh-modelmesh-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-openvino-model-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-spark-operator-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); and 12 more · Fixed: Red Hat build of Quarkus 3.27.4.SP1; Red Hat build of Quarkus 3.33.2.SP1
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 4.2.0.Final, < 4.2.15.Final; < 4.1.135.Final · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 4.2.0.Final, < 4.2.15.Final; < 4.1.135.Final · Fixed: Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-36455↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-5X3R-WRVG-RP6Q↗Official CVE record (CNA and ADP data)↗NVD record↗
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-47244 · cve.blacktree.nl