Read the docs

Denial of service in Moov signedxml XML canonicalization

Priority LOW 39CWE-400Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-400.

Summary

Moov signedxml before 1.4.1, including the Go module github.com/moov-io/signedxml, is affected. ExclusiveCanonicalization copies the full accumulated namespace map at every nested element before digest or signature checks, which is uncontrolled resource consumption (CWE-400). A remote unauthenticated attacker can send a small XML document with deeply nested elements and many unused namespace declarations through ValidateReferences, causing memory use to grow until the process terminates.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

Moov signedxml is a pure Go library for processing signed XML documents. Prior to 1.4.1, ExclusiveCanonicalization in exclusivecanonicalization.go copies the complete accumulated namespace map at every nested element before reference digest or signature checks. Attacker-controlled XML containing deeply nested elements with many unused namespace declarations causes quadratic allocation growth with depth and linear growth with prefixes per level, allowing a comparatively small document to consume multiple gigabytes of memory and terminate the process. The condition is reachable through ValidateReferences without a valid signature, matching certificate, or prior authentication, and it does not bypass signature verification. This issue is fixed in version 1.4.1.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00459 39th percentileScored 2026-11-07
Fix Fixed signedxml (moov-io): 1.4.1github.com/moov-io/signedxml (Go): 1.4.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
moov-iosignedxmlbefore 1.4.11.4.1Patch availableCNA
—github.com/moov-io/signedxml (Go)before 1.4.11.4.1Patch availableGHSA-5588-rp99-5fjh
  • signedxml Vendormoov-io Affected before 1.4.1 Fixed in 1.4.1 Patch available CNA
  • github.com/moov-io/signedxml (Go) Vendor— Affected before 1.4.1 Fixed in 1.4.1 Patch available GHSA-5588-rp99-5fjh

Remediation

Upgrade to version 1.4.1, the fixed version for the moov-io signedxml package and the github.com/moov-io/signedxml Go module.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA signedxml (moov-io) Fixed in 1.4.1
  • Fix · GHSA-5588-rp99-5fjh github.com/moov-io/signedxml (Go) Fixed in 1.4.1 Advisory →

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-113729
  2. 2026-10-21 Alias added: GHSA-5588-rp99-5fjh
  3. 2026-10-21 Fix available: Go/github.com/moov-io/[email protected] · GHSA-5588-rp99-5fjh
  4. 2026-10-21 CVSS score added · GHSA-5588-rp99-5fjh
  5. 2026-10-21 Weakness changed · GHSA-5588-rp99-5fjh
  6. 2026-10-21 5 new references · GHSA-5588-rp99-5fjh
  7. 2026-10-22 Priority changed: MEDIUM → LOW
  8. 2026-10-27 CISA SSVC decision points changed
  9. 2026-11-06 Affected versions changed · Red Hat
  10. 2026-11-06 CVSS score added · Red Hat

References

Sources