Goxmldsig Project Goxmldsig vulnerabilities
2 vulnerabilities
Known vulnerabilities in Goxmldsig Project Goxmldsig, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2020-15216debiangolang-github-russellhaering-goxmldsig+5
EPSS score0.90%
In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. A patch is available, all users of goxmldsig should upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64 or version 1.1.0CVE-2026-33487chainguardcommercial-grafana-11.6+74EPSS score0.42%
goxmlsig provides XML Digital Signatures implemented in Go. Prior to version 1.6.0, the `validateSignature` function in `validate.go` goes through the references in the `SignedInfo` block to find one that matches the signed element's ID. In Go versions before 1.22, or when `go.mod` uses an older version, there is a loop variable capture issue. The code takes the address of the loop variable `_ref` instead of its value. As a result, if more than one reference matches the ID or if the loop logic is incorrect, the `ref` pointer will always end up pointing to the last element in the `SignedInfo.References` slice after the loop. goxmlsig version 1.6.0 contains a patch.