goxmldsig: Improper Verification of Cryptographic Signature
CVE-2026-33487 is a high-severity improper verification of cryptographic signature vulnerability in goxmldsig from Russellhaering, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected goxmldsig versions: < 1.6.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.33% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of goxmldsig you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CNA (github.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | CNA |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
More Improper Verification of Cryptographic Signature vulnerabilities (CWE-347)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/russellhaering/goxmldsig/security/advisories/GHSA-479m-364c-43vcExploit, Mitigation
Other references
- access.redhat.com/errata/RHSA-2026:13548
- access.redhat.com/errata/RHSA-2026:20943
- access.redhat.com/errata/RHSA-2026:20946
- access.redhat.com/errata/RHSA-2026:21769
- access.redhat.com/errata/RHSA-2026:22347
- access.redhat.com/errata/RHSA-2026:22423
- access.redhat.com/errata/RHSA-2026:23345
- access.redhat.com/errata/RHSA-2026:36882
- access.redhat.com/security/cve/CVE-2026-33487
- bugzilla.redhat.com/show_bug.cgi?id=2451814
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33487.json
Recent Improper Verification of Cryptographic Signature vulnerabilities
- 9.1 Critical severity
- 9.0 Critical severity
- 7.5 High severity
- 9.1 Critical severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.