CVE-2026-56817: Netty: XML External Entity (XXE) injection via unconfigured XML factory when DTD and entity processing are enabled
Noroxi assessment
Priority: Monitor (action score 33/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.69% (FIRST EPSS); higher than 53.5% 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: io.netty:netty-codec-xml (Maven) 4.1.136.Final, 4.2.16.Final; netty (openSUSE:Tumbleweed) 4.1.136-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.80-150200.3.48.1.
Low priority for now. Upgrade to io.netty:netty-codec-xml (Maven) 4.1.136.Final, 4.2.16.Final; netty (openSUSE:Tumbleweed) 4.1.136-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.80-150200.3.48.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. In versions 4.2.0.Final through 4.2.15.Final and 4.1.0.Final through 4.1.135.Final, any caller that can deliver bytes to a Netty channel pipeline containing `XmlDecoder` can send XML with a `DOCTYPE` declaration to an `AsyncXMLInputFactory` instantiated with no security configuration, leaving DTD and entity handling active depending on Aalto XML async parser behavior and creating conditional XML external entity risk. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.
- Published
- Jul 21, 2026
- Updated
- Jul 30, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- CWE-611
Report tools
Action score
33
Low priority for now.
- CVSS
- 33 / 40 · 8.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N
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.
Is your version affected? Check itNoroxi 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 |
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.16.Final, >= 4.1.0.Final, < 4.1.136.Finalaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netty netty4.1.0 and later · before 4.1.136
- netty netty4.2.0 and later · before 4.2.16
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 | from 0 | — |
| Maven | io.netty:netty-codec-xml | from 4.1.0.Final · before 4.1.136.Final | 4.1.136.Final |
| Maven | io.netty:netty-codec-xml | from 4.2.0.Final · before 4.2.16.Final | 4.2.16.Final |
| openSUSE:Tumbleweed | netty | before 4.1.136-1.1 | 4.1.136-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | netty-tcnative | before 2.0.80-150200.3.48.1 | 2.0.80-150200.3.48.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP7 | netty | before 4.1.136-150200.4.53.1 | 4.1.136-150200.4.53.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…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-56746Jul 21, 2026 · Netty has a Security Control Bypass via CORS Short-Circuit Failure26Monitor
- ← EarlierCVE-2026-56816Jul 21, 2026 · Netty: Memory Exhaustion via HTTP/3 Reserved Frame Types30Monitor
- Later →CVE-2026-56819Jul 21, 2026 · Netty: HTTP/2 decompression leaks ByteBuf reference count when the decompressor channel is already closed (Direct memory leak / OOM DoS)30Monitor
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-codec-xml | 4.1.136.Final | Package registry (OSV) |
| Maven:io.netty:netty-codec-xml | 4.2.16.Final | Package registry (OSV) |
| opensuse:netty | 4.1.136-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:netty | 4.1.136-150200.4.53.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:netty-tcnative | 2.0.80-150200.3.48.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.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
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
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-611 · Improper Restriction of XML External Entity ReferenceCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.