Skip to main content
Vulnerability Database/CVE-2026-113729

CVE-2026-113729: Moov signedxml XML Parser DOS Vulnerability

CVE-2026-113729 is a denial of service vulnerability in Moov signedxml that allows attackers to exhaust memory through deeply nested XML elements. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113729 Overview

CVE-2026-113729 is a resource exhaustion vulnerability in Moov signedxml, a pure Go library for processing signed XML documents. Versions prior to 1.4.1 copy the complete accumulated namespace map at every nested element inside ExclusiveCanonicalization in exclusivecanonicalization.go. An attacker who submits crafted XML with deeply nested elements and many unused namespace declarations triggers quadratic memory growth with depth and linear growth with prefixes per level. A comparatively small document can consume multiple gigabytes of memory and terminate the host process. The condition is reachable through ValidateReferences without a valid signature, matching certificate, or prior authentication. The flaw is fixed in version 1.4.1.

Critical Impact

Unauthenticated attackers can crash any Go service that calls ValidateReferences by sending a single crafted XML payload, producing a reliable denial-of-service condition.

Affected Products

  • Moov signedxml versions prior to 1.4.1
  • Go applications and services embedding signedxml for SAML, XML digital signature, or WS-Security processing
  • Downstream libraries that invoke ExclusiveCanonicalization or ValidateReferences on untrusted XML

Discovery Timeline

  • 2026-10-20 - CVE-2026-113729 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-113729

Vulnerability Analysis

The vulnerability is a classic algorithmic complexity flaw classified as [CWE-400] Uncontrolled Resource Consumption. Exclusive XML Canonicalization (c14n) normalizes XML before signature verification. The Moov signedxml implementation tracks in-scope namespace declarations using a map that it copies at every descent into a child element. When input XML nests elements deeply and declares many unused namespace prefixes at each level, the per-level copy cost compounds. Memory use grows quadratically with nesting depth and linearly with the number of prefixes declared per element.

An attacker only needs to produce a modestly sized XML document to force gigabytes of allocation. The Go runtime terminates the process when the host exhausts memory, taking down any service that invoked the parser on the request.

Root Cause

The root cause lives in exclusivecanonicalization.go. The canonicalization routine copies the complete accumulated namespace map before processing each nested element rather than using an incremental or copy-on-write structure. Namespace declarations are retained regardless of whether any descendant element actually references them, which allows an attacker to inflate the per-node state cheaply.

Attack Vector

Exploitation requires only the ability to submit XML to any endpoint that passes it to ValidateReferences. No signing key, trusted certificate, or authenticated session is required because the canonicalization pass runs before signature validation. Typical reachable surfaces include SAML single sign-on endpoints, SOAP services using WS-Security, and any Go HTTP handler that forwards request bodies to the library.

The exploitation primitive is a single POST containing an XML document with a few hundred nested elements, each declaring dozens of unused xmlns: prefixes. No specific exploitation code is published by the vendor. For reproduction details, review the GitHub Security Advisory GHSA-5588 and the GitHub Commit Update.

Detection Methods for CVE-2026-113729

Indicators of Compromise

  • Sudden Go process termination with runtime: out of memory or OOM-killer entries in dmesg tied to XML-handling services
  • Spikes in resident set size on services that terminate shortly after receiving an XML POST
  • Inbound XML payloads containing unusually deep element nesting and numerous xmlns: declarations per element

Detection Strategies

  • Enable request body size and depth limits on reverse proxies in front of Go services that process signed XML
  • Inspect application logs for repeated short-lived container restarts correlated with XML endpoint traffic
  • Audit Go module graphs for github.com/moov-io/signedxml at versions below 1.4.1 using go list -m all

Monitoring Recommendations

  • Alert on container or pod OOMKilled events for workloads exposing SAML, SOAP, or XML signature endpoints
  • Track memory allocation rate and goroutine count on signedxml consumers; sudden allocation spikes without matching request volume indicate exploitation
  • Capture and retain representative XML request bodies for forensic review when OOM events occur

How to Mitigate CVE-2026-113729

Immediate Actions Required

  • Upgrade github.com/moov-io/signedxml to version 1.4.1 or later across all Go services
  • Rebuild and redeploy downstream binaries and container images that statically link the vulnerable version
  • Place inbound XML size, depth, and attribute-count limits at the ingress or WAF layer until the upgrade propagates

Patch Information

Moov released the fix in GitHub Release v1.4.1. The remediation is described in the GitHub Commit Update and tracked as GitHub Security Advisory GHSA-5588. Upgrade using go get github.com/moov-io/signedxml@v1.4.1 followed by go mod tidy.

Workarounds

  • Reject XML documents exceeding a conservative nesting depth (for example, 32 levels) before invoking ValidateReferences
  • Cap the number of namespace declarations per element and the total request body size at the HTTP layer
  • Run XML-processing workloads under per-process memory limits using cgroups or Kubernetes resource constraints to localize impact
bash
# Upgrade Moov signedxml to the patched release
go get github.com/moov-io/signedxml@v1.4.1
go mod tidy
go build ./...

# Verify the resolved version
go list -m github.com/moov-io/signedxml

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.