# CVE-2026-113729: Moov signedxml: Unauthenticated denial of service in exclusive XML canonicalization


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-5588-rp99-5fjh

## What is CVE-2026-113729?

CVE-2026-113729 is a high-severity vulnerability in moov-io signedxml, published on 20 Oct 2026. 

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-407 (Inefficient Algorithmic Complexity), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-113729?

2 open source packages ship an affected version, including github.com/moov-io/signedxml.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/moov-io/signedxml` | Go | All versions | 1.4.1 |
| `github.com/moov-io/signedxml` | Go | All versions | 1.4.1 |

## How do I fix CVE-2026-113729?

Upgrade github.com/moov-io/signedxml to 1.4.1 or later.

## Is CVE-2026-113729 being exploited?

There is no known exploitation of CVE-2026-113729 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113729 and fix it if it is affected.

What it is: CVE-2026-113729 is a high-severity vulnerability in moov-io signedxml, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113729 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/moov-io/signedxml (Go): affected all versions; fixed in 1.4.1
- github.com/moov-io/signedxml (Go): affected all versions; fixed in 1.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113729/ (Markdown: https://insights.sbomify.com/CVE-2026-113729/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113729
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113729
- OSV: https://osv.dev/vulnerability/CVE-2026-113729

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113729/
Summaries are generated and may contain mistakes; the official description above is the record.