On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-93569
- Name: Netty codec-http2: absolute-form Host mismatch translated to :authority
- Severity: High
- CVSS: 8.2 (v3.1) (High)
- CVSS version: 3.1
- CVSS source: redhat CNA
- CVSS vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: Low
- Integrity impact: High
- Availability impact: None
- CWE: CWE-444 — Inconsistent Interpretation of HTTP Requests (‘HTTP Request/Response Smuggling’)
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-273 (opens in a new tab) , CAPEC-33 (opens in a new tab)
- Vendor: netty
- Vulnerable product: netty-codec-http2
- CVE published: 2026-09-18
- CVE last modified: 2026-10-19
- EPSS: 0.0219; 82.3th percentile as of 2026-10-21 (FIRST (opens in a new tab) )
- Latest Update: 2026-10-14
- Reviewed Rule IDs: 340364
- Reviewed rules with current blocking actions: 340364
- Request surfaces inspected: Request headers
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v3.1 · secalert@redhat.com
- Base score: 8.2
- Base severity: HIGH
- Exploitability subscore: 3.9
- Impact subscore: 4.2
- Assessment type: Secondary
- Source identifier: secalert@redhat.com
- Full vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: Low
- Integrity impact: High
- Availability impact: None
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-09-22T14:36:45.463553Z
- Exploitation: none
- Automatable: yes
- Technical Impact: partial
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.
Vulnerability Description
A flaw was found in Netty. A remote unauthenticated attacker can exploit a vulnerability in Netty’s HTTP/1 to HTTP/2 conversion process. When an HTTP/1 request includes both an absolute-form request-target and a conflicting Host header, Netty incorrectly prioritizes the Host header for the HTTP/2 :authority field, discarding the original request-target authority. This inconsistency can allow an attacker to bypass security controls in Netty-based proxies or gateways, potentially leading to unauthorized access, cache poisoning, or misrouting of requests.
Recommended Actions
Maintain the reviewed Atomicorp rules. Keep your Atomicorp commercial rules current and confirm that the reviewed rules (340364 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Versions reported unaffected: Red Hat Red Hat Build of Apache Camel 3.33.3.SP2 version 4.1.138.Final-redhat-00001.
- CNA guidance source: redhat (opens in a new tab)
- Vendor workaround: See https://github.com/netty/netty/security/advisories/GHSA-cg2g-fxr4-mg8m (opens in a new tab) for fixed versions and remediation guidance.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://access.redhat.com/errata/RHSA-2026:69440 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/errata/RHSA-2026:69470 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/errata/RHSA-2026:70257 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/errata/RHSA-2026:83612 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/security/cve/CVE-2026-93569 (opens in a new tab)
- CVE authority reference: https://bugzilla.redhat.com/show_bug.cgi?id=2536962 (opens in a new tab)
Test or Research Source
- Source: https://access.redhat.com/errata/RHSA-2026:69440 (opens in a new tab)
- Tags: manual-review
- Research basis: Every supported web server rejects a request that carries more than one Host header before forwarding it, and Atomicorp rule 340364 enforces the same check on any platform that does not.
- Notes: Platform-mitigated special case (Mike, 2026-10-14): the CVE needs two Host lines, or :authority plus a literal Host, to reach the vulnerable listener. Apache 2.4.62, Caddy 2.11.7 and Varnish 6.0/9.1 were measured rejecting that with 400 before ModSecurity runs; nginx per its source. A proxy forwards one Host downstream regardless. 340364 is defense in depth; a replay in which the request reaches ModSecurity and 340364 does not fire is the regression to alarm on.
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .