CVE-2026-56859: CWE-770: Allocation of Resources Without Limits or Throttling in Go standard library encoding/xml
CVE-2026-56859 is a vulnerability in the Go standard library's encoding/xml package. The issue arises because the DecodeElement function resets the depth counter improperly, preventing it from triggering as intended. This flaw can lead to unbounded resource allocation, specifically stack exhaustion, when processing XML data. The vulnerability affects multiple versions of the Go standard library, including versions prior to 1.25.13, exactly 1.26.0-0 and 1.27.0-0, and versions from 1.26.0-0 up to but not including 1.26.6. No official patch or remediation guidance is currently available. There are no known exploits in the wild at this time.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-56859 in the Go standard library encoding/xml package involves improper handling of the depth counter in the DecodeElement function. Previously, the function would reset the depth counter, causing it never to fire and thus failing to limit resource allocation. This can result in stack exhaustion due to unbounded recursion or resource use when parsing XML. The affected versions include all versions before 1.25.13, version 1.26.0-0, versions from 1.26.0-0 up to but excluding 1.26.6, and version 1.27.0-0. No CVSS score or vendor advisory patch information is currently available, and no known active exploitation has been reported.
Potential Impact
The vulnerability can cause stack exhaustion in applications using the affected versions of the Go encoding/xml package, potentially leading to denial of service or application crashes due to resource exhaustion. There is no evidence of active exploitation in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider mitigating risk by limiting exposure to untrusted XML input or applying application-level resource constraints. Monitor official Go project communications for updates on patches or workarounds.
CVE-2026-56859: CWE-770: Allocation of Resources Without Limits or Throttling in Go standard library encoding/xml
Description
CVE-2026-56859 is a vulnerability in the Go standard library's encoding/xml package. The issue arises because the DecodeElement function resets the depth counter improperly, preventing it from triggering as intended. This flaw can lead to unbounded resource allocation, specifically stack exhaustion, when processing XML data. The vulnerability affects multiple versions of the Go standard library, including versions prior to 1.25.13, exactly 1.26.0-0 and 1.27.0-0, and versions from 1.26.0-0 up to but not including 1.26.6. No official patch or remediation guidance is currently available. There are no known exploits in the wild at this time.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-56859 in the Go standard library encoding/xml package involves improper handling of the depth counter in the DecodeElement function. Previously, the function would reset the depth counter, causing it never to fire and thus failing to limit resource allocation. This can result in stack exhaustion due to unbounded recursion or resource use when parsing XML. The affected versions include all versions before 1.25.13, version 1.26.0-0, versions from 1.26.0-0 up to but excluding 1.26.6, and version 1.27.0-0. No CVSS score or vendor advisory patch information is currently available, and no known active exploitation has been reported.
Potential Impact
The vulnerability can cause stack exhaustion in applications using the affected versions of the Go encoding/xml package, potentially leading to denial of service or application crashes due to resource exhaustion. There is no evidence of active exploitation in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should consider mitigating risk by limiting exposure to untrusted XML input or applying application-level resource constraints. Monitor official Go project communications for updates on patches or workarounds.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Go
- Date Reserved
- 2026-06-23T15:10:49.353Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e412ebf8831d539e05125
Added to database: 08/13/2026, 22:11:58 UTC
Last enriched: 08/13/2026, 22:27:47 UTC
Last updated: 08/13/2026, 23:23:42 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.