CVE-2026-33487 — Russellhaering Goxmldsig vulnerability

Vendor	Product	Version range	Fixed in
github.com	russellhaering_goxmldsig	>= 0 < 1.6.0	1.6.0
goxmldsig_project	goxmldsig	< 1.6.0	1.6.0
russellhaering	goxmldsig	< 1.6.0	1.6.0

VulDB

russellhaering goxmldsig up to 1.5.x XML Digital Signature validateSignature signature verification (Nessus ID 304089)

vuldb·2026-07-01·CVSS 7.5

CVE-2026-33487 [HIGH] russellhaering goxmldsig up to 1.5.x XML Digital Signature validateSignature signature verification (Nessus ID 304089) A vulnerability, which was classified as problematic, was found in russellhaering goxmldsig up to 1.5.x. Affected by this issue is the function validateSignature of the component XML Digital Signature Handler. Such manipulation leads to improper verification of cryptographic signature. This vulnerability is traded as CVE-2026-33487. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.

OSV

Loop Variable Capture Signature Bypass in goxmldsig in github.com/russellhaering/goxmldsig

osv·2026-03-27

CVE-2026-33487 Loop Variable Capture Signature Bypass in goxmldsig in github.com/russellhaering/goxmldsig Loop Variable Capture Signature Bypass in goxmldsig in github.com/russellhaering/goxmldsig Loop Variable Capture Signature Bypass in goxmldsig in github.com/russellhaering/goxmldsig

GHSA

validateSignature Loop Variable Capture Signature Bypass in goxmldsig

ghsa·2026-03-18

CVE-2026-33487 [HIGH] CWE-347 validateSignature Loop Variable Capture Signature Bypass in goxmldsig validateSignature Loop Variable Capture Signature Bypass in goxmldsig ### Details 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. ### Technical Details The code takes the address of a loop iteration variable (&_ref). In the standard Go compiler, this variable is only allocated once for the whol

OSV

validateSignature Loop Variable Capture Signature Bypass in goxmldsig

osv·2026-03-18

CVE-2026-33487 [HIGH] validateSignature Loop Variable Capture Signature Bypass in goxmldsig validateSignature Loop Variable Capture Signature Bypass in goxmldsig ### Details 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. ### Technical Details The code takes the address of a loop iteration variable (&_ref). In the standard Go compiler, this variable is only allocated once for the whol

Red Hat

github.com/russellhaering/goxmldsig: goxmlsig: Integrity bypass due to incorrect XML Digital Signature validation via loop variable capture issue

vendor_redhat·2026-03-26·CVSS 7.5

CVE-2026-33487 [HIGH] CWE-347 github.com/russellhaering/goxmldsig: goxmlsig: Integrity bypass due to incorrect XML Digital Signature validation via loop variable capture issue github.com/russellhaering/goxmldsig: goxmlsig: Integrity bypass due to incorrect XML Digital Signature validation via loop variable capture issue 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.

CVE-2026-33487: goxmlsig provides XML Digital Signatures implemented in Go. Prior to version 1.6.0, the `validateSignature` function in `validate.go` goes through the…

Affected

CVSS provenance