How severe is CVE-2026-33487?

CVE-2026-33487 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-33487 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-33487?

CVE-2026-33487 affects Goxmldsig Project Goxmldsig. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-33487?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-33487 have an EU (EUVD) identifier?

Yes. CVE-2026-33487 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-16281.

When was CVE-2026-33487 published?

CVE-2026-33487 was published on 2026-03-26 and last updated on 2026-06-30.

CVE-2026-33487

CVE-2026-33487 is a high-severity vulnerability in Goxmldsig Project Goxmldsig with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-347.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (22nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-16281
Weakness: CWE-347
Affected product: Goxmldsig Project Goxmldsig
Published: 2026-03-26
Last modified: 2026-06-30

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.

Frequently asked questions

What is 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 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.
How severe is CVE-2026-33487?: CVE-2026-33487 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-33487 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-33487?: CVE-2026-33487 affects Goxmldsig Project Goxmldsig. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-33487?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-33487 have an EU (EUVD) identifier?: Yes. CVE-2026-33487 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-16281.
When was CVE-2026-33487 published?: CVE-2026-33487 was published on 2026-03-26 and last updated on 2026-06-30.

References

Affected products (1)

cpe:2.3:a:goxmldsig_project:goxmldsig:*:*:*:*:*:*:*:*

More vulnerabilities in Goxmldsig Project Goxmldsig

CVE-2020-7711 — High (CVSS 7.5): This affects all versions of package github.com/russellhaering/goxmldsig. There is a crash on nil-pointer dereference…
CVE-2020-15216 — Medium (CVSS 5.3): In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file,…

All CVEs affecting Goxmldsig Project Goxmldsig →

Other CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities

CVE-2026-48558 — Critical (CVSS 10.0): SimpleHelp versions 5.5.15 and prior and 6.0 pre-release versions contain an authentication bypass vulnerability in the…
CVE-2023-25574 — Critical (CVSS 10.0): `jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI).…
CVE-2024-45409 — Critical (CVSS 10.0): The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <=…
CVE-2024-32962 — Critical (CVSS 10.0): xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default…
CVE-2022-24884 — Critical (CVSS 10.0): ecdsautils is a tiny collection of programs used for ECDSA (keygen, sign, verify). `ecdsa_verify_[prepare_]legacy()`…
CVE-2021-33885 — Critical (CVSS 10.0): An Insufficient Verification of Data Authenticity vulnerability in B. Braun SpaceCom2 prior to 012U000062 allows a…

Browse all CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities →