CVE-2026-56817

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 30, 2026

Advisory Details (5)

Auto-updated Sep 10, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

XML: Injection / Risky Sink — unconfigured XML factory with active DTD and entity handling · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-4qhr-g3c6-fcfx
github_release Patch Available

netty-4.2.16.Final

Patch available: netty/netty netty-4.2.16.Final

https://github.com/netty/netty/releases/tag/netty-4.2.16.Final
github_release Patch Available

netty-4.1.136.Final

Patch available: netty/netty netty-4.1.136.Final

https://github.com/netty/netty/releases/tag/netty-4.1.136.Final
github_commit Patch Available

commit bb2ff68a1fb7 (netty/netty)

Patch available: netty/netty netty-4.1.136.Final (contains commit bb2ff68a1fb7)

https://github.com/netty/netty/commit/bb2ff68a1fb71cb4b0eb9a9e17b66c52aff680c6
github_commit Patch Available

commit 5b68c61f37aa (netty/netty)

Patch available: netty/netty netty-4.2.16.Final (contains commit 5b68c61f37aa)

https://github.com/netty/netty/commit/5b68c61f37aa4a3045cba624cbea239655c9003b

Vendor Advisories for CVE-2026-56817(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-xml2026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)——
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-xml4.1.0.Final ... 4.1.99.Final (136 versions)4.1.136.Final—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 148× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 223 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-14 17:06 UTCVendor advisory
  3. 2026-09-14 10:51 UTCVendor advisory
  4. 2026-09-14 06:45 UTCVendor advisory
  5. 2026-09-14 02:39 UTCVendor advisory
  6. 2026-09-13 22:27 UTCVendor advisory
  7. 2026-09-13 17:51 UTCEG score recompute
  8. 2026-09-13 17:51 UTCVendor advisory
  9. 2026-09-13 16:47 UTCEPSS rescore
  10. 2026-09-13 13:45 UTCVendor advisory
  11. 2026-09-13 09:39 UTCVendor advisory
  12. 2026-09-13 05:33 UTCVendor advisory
  13. 2026-09-13 01:27 UTCVendor advisory
  14. 2026-09-12 20:57 UTCVendor advisory
  15. 2026-09-12 16:38 UTCEG score recompute
  16. 2026-09-12 16:38 UTCVendor advisory
  17. 2026-09-12 12:32 UTCVendor advisory
  18. 2026-09-12 06:40 UTCVendor advisory
  19. 2026-09-12 02:20 UTCVendor advisory
  20. 2026-09-11 22:06 UTCVendor advisory
  21. 2026-09-11 17:52 UTCEG score recompute
  22. 2026-09-11 17:52 UTCVendor advisory
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 07:24 UTCVendor advisory
  25. 2026-09-11 03:18 UTCVendor advisory
Show 75 more
  1. 2026-09-10 22:06 UTCEG score recompute
  2. 2026-09-10 22:06 UTCVendor advisory
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-09 09:20 UTCEG score recompute
  5. 2026-09-09 09:20 UTCVendor advisory
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-08 01:50 UTCVendor advisory
  8. 2026-09-07 21:44 UTCEG score recompute
  9. 2026-09-07 21:44 UTCVendor advisory
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 16:59 UTCEG score recompute
  12. 2026-09-06 16:59 UTCVendor advisory
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 12:52 UTCVendor advisory
  15. 2026-09-06 08:46 UTCVendor advisory
  16. 2026-09-06 03:58 UTCVendor advisory
  17. 2026-09-05 23:43 UTCVendor advisory
  18. 2026-09-05 19:36 UTCEG score recompute
  19. 2026-09-05 19:36 UTCVendor advisory
  20. 2026-09-05 07:17 UTCEG score recompute
  21. 2026-09-05 07:17 UTCVendor advisory
  22. 2026-09-04 14:00 UTCEG score recompute
  23. 2026-09-04 14:00 UTCVendor advisory
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-02 14:12 UTCEPSS rescore
  26. 2026-09-01 23:43 UTCEG score recompute
  27. 2026-09-01 23:43 UTCVendor advisory
  28. 2026-09-01 13:54 UTCEPSS rescore
  29. 2026-09-01 04:40 UTCEPSS rescore
  30. 2026-08-31 07:55 UTCVendor advisory
  31. 2026-08-31 03:01 UTCVendor advisory
  32. 2026-08-30 22:54 UTCEG score recompute
  33. 2026-08-30 22:54 UTCVendor advisory
  34. 2026-08-30 19:17 UTCEPSS rescore
  35. 2026-08-30 18:48 UTCVendor advisory
  36. 2026-08-30 14:42 UTCVendor advisory
  37. 2026-08-30 10:27 UTCVendor advisory
  38. 2026-08-30 05:09 UTCEG score recompute
  39. 2026-08-30 05:09 UTCVendor advisory
  40. 2026-08-30 01:22 UTCEPSS rescore
  41. 2026-08-30 00:59 UTCEG score recompute
  42. 2026-08-30 00:59 UTCVendor advisory
  43. 2026-08-28 21:42 UTCEPSS rescore
  44. 2026-08-28 01:33 UTCVendor advisory
  45. 2026-08-27 21:10 UTCVendor advisory
  46. 2026-08-27 14:31 UTCEG score recompute
  47. 2026-08-27 14:31 UTCVendor advisory
  48. 2026-08-27 14:25 UTCEPSS rescore
  49. 2026-08-27 10:20 UTCVendor advisory
  50. 2026-08-27 04:55 UTCVendor advisory
  51. 2026-08-27 00:07 UTCVendor advisory
  52. 2026-08-26 19:59 UTCEG score recompute
  53. 2026-08-26 19:59 UTCVendor advisory
  54. 2026-08-26 14:46 UTCEPSS rescore
  55. 2026-08-26 11:57 UTCVendor advisory
  56. 2026-08-26 07:51 UTCVendor advisory
  57. 2026-08-26 03:41 UTCVendor advisory
  58. 2026-08-25 23:35 UTCVendor advisory
  59. 2026-08-25 19:01 UTCVendor advisory
  60. 2026-08-25 14:54 UTCEG score recompute
  61. 2026-08-25 14:54 UTCVendor advisory
  62. 2026-08-25 13:49 UTCEPSS rescore
  63. 2026-08-25 10:48 UTCVendor advisory
  64. 2026-08-25 06:42 UTCVendor advisory
  65. 2026-08-25 02:30 UTCVendor advisory
  66. 2026-08-24 22:24 UTCVendor advisory
  67. 2026-08-24 18:18 UTCEG score recompute
  68. 2026-08-24 18:18 UTCVendor advisory
  69. 2026-08-24 13:53 UTCVendor advisory
  70. 2026-08-24 09:47 UTCEG score recompute
  71. 2026-08-24 09:47 UTCVendor advisory
  72. 2026-08-24 05:40 UTCVendor advisory
  73. 2026-08-24 01:34 UTCVendor advisory
  74. 2026-08-23 21:26 UTCVendor advisory
  75. 2026-08-23 17:20 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56817?
CVE-2026-56817 is a critical vulnerability published on July 21, 2026. 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…
When was CVE-2026-56817 disclosed?
CVE-2026-56817 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56817 actively exploited?
CVE-2026-56817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.4% of all scored CVEs.
What is the CVSS score of CVE-2026-56817?
CVE-2026-56817 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-56817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56817, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56817

Explore →

Is Your Infrastructure Affected by CVE-2026-56817?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs