CVE-2026-33487: CWE-347: Improper Verification of Cryptographic Signature in russellhaering goxmldsig
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.
AI Analysis
Technical Summary
The vulnerability arises from a programming error in the validateSignature function of goxmldsig, where the address of a loop variable is taken instead of its value. This causes the reference pointer to always point to the last element in the SignedInfo.References slice after the loop, potentially allowing incorrect signature validation. This flaw affects goxmldsig versions before 1.6.0 and Go versions prior to 1.22 or projects using older go.mod versions. The issue is tracked as CWE-347 (Improper Verification of Cryptographic Signature) and CWE-682 (Incorrect Calculation). The vulnerability has a CVSS v3.1 base score of 7.5 (high severity) with network attack vector, low complexity, no privileges or user interaction required, and results in high integrity impact. Red Hat advisories confirm the vulnerability and provide security updates for affected products. A fixed version (1.6.0) of goxmldsig is available.
Potential Impact
An attacker could exploit this vulnerability to bypass integrity checks on XML Digital Signatures, potentially allowing unauthorized modification of signed data without detection. This compromises the integrity of applications relying on goxmldsig for XML signature validation. The vulnerability does not affect confidentiality or availability but has a high impact on data integrity.
Mitigation Recommendations
A fix is available in goxmldsig version 1.6.0. Users should upgrade to version 1.6.0 or later to remediate this vulnerability. Red Hat has released security advisories and updates addressing this issue in their affected products. No alternative mitigations meeting Red Hat's criteria are currently available. Users of affected Red Hat products should apply the provided security updates as soon as possible.
CVE-2026-33487: CWE-347: Improper Verification of Cryptographic Signature in russellhaering goxmldsig
Description
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.
CVSS v3.1
Score 7.5high
Affected software
russellhaering
goxmldsig
pkg:golang/github.com/russellhaering/goxmldsigRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from a programming error in the validateSignature function of goxmldsig, where the address of a loop variable is taken instead of its value. This causes the reference pointer to always point to the last element in the SignedInfo.References slice after the loop, potentially allowing incorrect signature validation. This flaw affects goxmldsig versions before 1.6.0 and Go versions prior to 1.22 or projects using older go.mod versions. The issue is tracked as CWE-347 (Improper Verification of Cryptographic Signature) and CWE-682 (Incorrect Calculation). The vulnerability has a CVSS v3.1 base score of 7.5 (high severity) with network attack vector, low complexity, no privileges or user interaction required, and results in high integrity impact. Red Hat advisories confirm the vulnerability and provide security updates for affected products. A fixed version (1.6.0) of goxmldsig is available.
Potential Impact
An attacker could exploit this vulnerability to bypass integrity checks on XML Digital Signatures, potentially allowing unauthorized modification of signed data without detection. This compromises the integrity of applications relying on goxmldsig for XML signature validation. The vulnerability does not affect confidentiality or availability but has a high impact on data integrity.
Mitigation Recommendations
A fix is available in goxmldsig version 1.6.0. Users should upgrade to version 1.6.0 or later to remediate this vulnerability. Red Hat has released security advisories and updates addressing this issue in their affected products. No alternative mitigations meeting Red Hat's criteria are currently available. Users of affected Red Hat products should apply the provided security updates as soon as possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-20T16:16:48.971Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-33487","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22423","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22347","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:21769","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:23345","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:13548","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20946","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:20943","vendor":"Red Hat"}]
Threat ID: 69c570d8f4197a8e3bef1efc
Added to database: 03/26/2026, 17:46:00 UTC
Last enriched: 08/17/2026, 13:16:51 UTC
Last updated: 09/10/2026, 20:31:02 UTC
Views: 165
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.