Netty: DNS Cache Poisoning due to Predictable PRNG and Default Static Source Port
Noroxi assessment
Priority: Monitor (action score 27/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.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: io.netty:netty-resolver-dns (Maven) 4.2.15.Final, 4.1.135.Final; netty (openSUSE:Tumbleweed) 4.1.135-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.79-150200.3.45.1.
Low priority for now. Upgrade to io.netty:netty-resolver-dns (Maven) 4.2.15.Final, 4.1.135.Final; netty (openSUSE:Tumbleweed) 4.1.135-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.79-150200.3.45.1 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 is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DNS resolver uses a predictable PRNG for generating DNS transaction IDs and defaults to a static UDP source port. This combination reduces the entropy of DNS queries, enabling DNS Cache Poisoning (Kaminsky attack). Versions 4.1.135.Final and 4.2.15.Final patch the issue.
- Published
- Jun 12, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 32th percentile
- CWE
- CWE-330
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.8
- NVD has not scored this yet; the score shown is the CNA’s.
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.
| Vendor | Product | CPE |
|---|---|---|
| netty | netty | cpe:2.3:a:netty:netty |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netty nettybefore 4.1.135
- netty netty4.2.0 and later · before 4.2.15
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.2.0.Final, < 4.2.15.Final, < 4.1.135.Finalaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | netty | all versions | — |
| Maven | io.netty:netty-resolver-dns | from 4.2.0.Final · before 4.2.15.Final | 4.2.15.Final |
| Maven | io.netty:netty-resolver-dns | before 4.1.135.Final | 4.1.135.Final |
| openSUSE:Tumbleweed | netty | before 4.1.135-1.1 | 4.1.135-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | netty-tcnative | before 2.0.79-150200.3.45.1 | 2.0.79-150200.3.45.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | netty | before 4.1.135-150200.4.50.1 | 4.1.135-150200.4.50.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
- CVE-2026-42581Netty: HTTP/1.0 TE+CL Coexistence Bypasses Smuggling Sanitization39Monitor
- CVE-2019-20444HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with39Monitor
- CVE-2026-75595Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext36Monitor
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 |
|---|---|---|
| Maven:io.netty:netty-resolver-dns | 4.1.135.Final | Package registry (OSV) |
| Maven:io.netty:netty-resolver-dns | 4.2.15.Final | Package registry (OSV) |
| opensuse:netty | 4.1.135-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:netty | 4.1.135-150200.4.50.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:netty-tcnative | 2.0.79-150200.3.45.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-330 · Use of Insufficiently Random ValuesCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.