This page was not yet optimized for use on mobile devices.
CVE-2026-42582
Data
| Vulnerability ID | CVE-2026-42582 |
|---|---|
| Published on | 13.05.2026 19:17 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:netty:netty:4.2.0:-:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:alpha2:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:alpha3:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:alpha4:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:alpha5:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:alpha6:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:netty:netty:4.2.0:rc2:*:*:*:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.