Cyber Resilience

CVE-2026-56817

XXE in Netty 4.1.0 – 4.1.136

XXE
Published
21 July 2026
Modified
30 July 2026
Patch / advisory
View advisory
CVSS Score v4 8.3
Click a component to see what it means
Raw vectorCVSS: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
EPSS Score 0.0032 24th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-56817 is a high-severity Improper Restriction of XML External Entity Reference (CWE-611) vulnerability in Netty Netty. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

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…

more

`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.

CWE(s)
CWE-611

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

XXE flaw in Netty XML decoder directly enables remote exploitation of public-facing applications by sending crafted DOCTYPE XML over the network.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-54470Shared CWE-611
CVE-2024-49352Shared CWE-611
CVE-2026-44618Shared CWE-611
CVE-2026-12975Shared CWE-611
CVE-2026-51080Shared CWE-611
CVE-2024-2374Shared CWE-611
CVE-2026-41895Shared CWE-611
CVE-2026-13449Shared CWE-611
CVE-2025-64518Shared CWE-611
CVE-2025-6438Shared CWE-611

Affected Assets

netty
netty
4.1.0 — 4.1.136 · 4.2.0 — 4.2.16

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.1
  • V15.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

CA-8 Penetration Testing
addresses: CWE-611

Penetration testing includes XML external entity payloads, detecting XXE vulnerabilities and enabling their mitigation.

SI-4 System Monitoring
addresses: CWE-611

Identifies XML external entity processing via monitoring of unusual file/network access or resource usage.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Hardened XML parser configurations directly disable external entity resolution.

PR.PS-06 mostly match
prevents

Secure SDLC practices include input validation and safe XML parser configuration that prevent XXE.

ID.RA-01 partial match
prevents

Vulnerability scanning can discover XXE flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Patching eliminates XXE-vulnerable parser versions but is only one aspect of software maintenance.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches XXE via static analysis and dynamic XML fuzzing.

A.8.8 Management of technical vulnerabilities mostly match
detects

Vulnerability management identifies and patches XML libraries with unsafe default entity settings.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and entity handling that directly prevents XXE.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for disabling external entity processing in XML parsers.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include safe parser configuration that mitigates external entity risks.

A.8.28 Secure coding partial match
prevents

Secure coding standards require disabling DTDs and external entities in XML processing.

References