CVE-2022-41915: Netty project is an event-driven asynchronous network application framework.
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.95% (FIRST EPSS); higher than 61.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: netty netty 4.1.86.Final.
Low priority for now. Upgrade to netty netty 4.1.86.Final or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Netty project is an event-driven asynchronous network application framework. Starting in version 4.1.83.Final and prior to 4.1.86.Final, when calling `DefaultHttpHeadesr.set` with an _iterator_ of values, header value validation was not performed, allowing malicious header values in the iterator to perform HTTP Response Splitting. This issue has been patched in version 4.1.86.Final. Integrators can work around the issue by changing the `DefaultHttpHeaders.set(CharSequence, Iterator<?>)` call, into a `remove()` call, and call `add()` in a loop over the iterator of values.
- Published
- Dec 13, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 61th percentile
- CWE
- CWE-113
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · GitHub_M
- 6.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux11.0
- netty netty4.1.83 and later · before 4.1.86
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
netty netty
- 4.1.86.Final and later · before 4.1.86.Finalaffected
- 4.1.83.Final and later · before 4.1.83.Final*affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | netty | before 1:4.1.33-1+deb10u3 | 1:4.1.33-1+deb10u3 |
| Debian:11 | netty | before 1:4.1.48-4+deb11u1 | 1:4.1.48-4+deb11u1 |
| Debian:12 | netty | before 1:4.1.48-6 | 1:4.1.48-6 |
| Maven | io.netty:netty-codec-http | from 4.1.83.Final · before 4.1.86.Final | 4.1.86.Final |
| openSUSE:Leap 15.4 | netty | before 4.1.90-150200.4.14.1 | 4.1.90-150200.4.14.1 |
| openSUSE:Leap 15.4 | netty-tcnative | before 2.0.59-150200.3.10.1 | 2.0.59-150200.3.10.1 |
| openSUSE:Tumbleweed | netty | before 4.1.114-1.1 | 4.1.114-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | netty-tcnative | before 2.0.59-150200.3.10.1 | 2.0.59-150200.3.10.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP5 | netty | before 4.1.90-150200.4.14.1 | 4.1.90-150200.4.14.1 |
Same product
netty: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-47691Netty has Insufficient Bailiwick Validation for NS Records40Plan
- CVE-2026-45674Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records40Plan
- CVE-2019-20445HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Tr40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-24823May 6, 2022 · Local Information Disclosure Vulnerability in io.netty:netty-codec-http22Monitor
- ← EarlierCVE-2022-41881Dec 12, 2022 · Netty project is an event-driven asynchronous network application framework.30Monitor
- Later →CVE-2023-34462Jun 22, 2023 · netty-handler SniHandler 16MB allocation27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| netty netty | 4.1.86.Final · description | Vendor (CNA) |
| debian:netty | 1:4.1.48-6 · Debian:12 | Package registry (OSV) |
| Maven:io.netty:netty-codec-http | 4.1.86.Final | Package registry (OSV) |
| opensuse:netty | 4.1.90-150200.4.14.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:netty-tcnative | 2.0.59-150200.3.10.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:netty | 4.1.90-150200.4.14.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP5 | Package registry (OSV) |
| suse:netty-tcnative | 2.0.59-150200.3.10.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-113 · Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.