How severe is CVE-2022-41915?

CVE-2022-41915 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-41915?

CVE-2022-41915 affects the following packages: io.netty:netty-codec-http (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-41915?

Update io.netty:netty-codec-http to 4.1.86.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41915 is resolved across your whole dependency graph.

How do I detect CVE-2022-41915 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty:netty-codec-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-41915 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-41915 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-41915, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-41915?

CVE-2022-41915 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-41915?

CVE-2022-41915 is classified as CWE-113 (CWE-113), CWE-436 (CWE-436). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-41915 published, and has it been updated?

CVE-2022-41915 was published on December 13, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-41915 — netty-codec-http

MEDIUMFix: netty/netty@fe18adf

CVE-2022-41915 is a medium-severity (CVSS 6.5) CWE-113 vulnerability in io.netty:netty-codec-http. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for io.netty:netty-codec-http — see the affected versions and patch details below.

Netty vulnerable to HTTP Response splitting from assigning header value iterator

Also known asGHSA-hh82-3pmq-7frp

Published

Dec 13, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕io.netty:netty-codec-http

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When calling DefaultHttpHeaders.set with an iterator of values (as opposed to a single given value), header value validation was not performed, allowing malicious header values in the iterator to perform HTTP Response Splitting.

Patches

The necessary validation was added in Netty 4.1.86.Final.

Workarounds

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.

References

HTTP Response Splitting CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers

For more information

If you have any questions or comments about this advisory:

Open an issue in [example link to repo](https://github.com/netty/netty)
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.netty:netty-codec-http`	≥ 4.1.83.Final&&< 4.1.86.Final	4.1.86.Final`io.netty:netty-codec-http:4.1.86.Final`

Affected Products

2 products · 3 configurations

debian linuxdebian

2 versions

10.011.0

Application

nettynetty

≥ 4.1.83 && < 4.1.86

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Netty project is an event-driven asynchronous network application framew…

github.comNVDMar 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty:netty-codec-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.netty:netty-codec-http to 4.1.86.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41915 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact When calling `DefaultHttpHeaders.set` with an _iterator_ of values (as opposed to a single given value), header value validation was not performed, allowing malicious header values in the iterator to perform [HTTP Response Splitting](https://owasp.org/www-community/attacks/HTTP_Response_Splitting). ### Patches The necessary validation was added in Netty 4.1.86.Final. ### Workarounds 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. ### Refe