CVE-2026-33487

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

March 26, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 10, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

validateSignature Loop Variable Capture Signature Bypass in goxmldsig · Advisory · russellhaering/goxmldsig · GitHub

https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-479m-364c-43vc

Vendor Advisories for CVE-2026-33487(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/acm-grafana-rhel9:17826933862026-07-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17801671182026-06-04redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17792122592026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17795794392026-06-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17788677532026-05-28redhat
redhatopenshift-gitops-1/dex-rhel8:17791163592026-05-26redhat
redhatopenshift-gitops-1/dex-rhel8:17792099652026-05-26redhat
redhatrhacm2/acm-grafana-rhel9:17771422692026-05-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/russellhaering/goxmldsig—1.6.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 82× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 197 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 13:25 UTCEG score recompute
  3. 2026-08-25 13:25 UTCVendor advisory
  4. 2026-08-25 12:22 UTCEG score recompute
  5. 2026-08-25 12:22 UTCVendor advisory
  6. 2026-08-24 14:17 UTCEPSS rescore
  7. 2026-08-24 13:31 UTCEG score recompute
  8. 2026-08-24 13:31 UTCVendor advisory
  9. 2026-08-24 12:27 UTCEG score recompute
  10. 2026-08-24 12:27 UTCVendor advisory
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 12:21 UTCEG score recompute
  19. 2026-08-17 12:21 UTCVendor advisory
  20. 2026-08-17 12:13 UTCEG score recompute
  21. 2026-08-17 12:13 UTCVendor advisory
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 10:07 UTCEG score recompute
  24. 2026-08-16 10:07 UTCVendor advisory
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:55 UTCEG score recompute
  2. 2026-08-15 01:55 UTCVendor advisory
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 13:28 UTCEG score recompute
  5. 2026-08-14 13:28 UTCVendor advisory
  6. 2026-08-14 12:30 UTCEG score recompute
  7. 2026-08-14 12:30 UTCVendor advisory
  8. 2026-08-14 06:25 UTCEG score recompute
  9. 2026-08-14 06:25 UTCVendor advisory
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-12 20:42 UTCEG score recompute
  12. 2026-08-12 20:42 UTCVendor advisory
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-11 20:49 UTCEG score recompute
  15. 2026-08-11 20:49 UTCVendor advisory
  16. 2026-08-11 03:51 UTCEG score recompute
  17. 2026-08-11 03:51 UTCVendor advisory
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 13:22 UTCEG score recompute
  20. 2026-08-10 13:22 UTCVendor advisory
  21. 2026-08-10 12:27 UTCEG score recompute
  22. 2026-08-10 12:27 UTCVendor advisory
  23. 2026-08-10 06:47 UTCVendor advisory
  24. 2026-08-09 18:22 UTCEG score recompute
  25. 2026-08-09 18:22 UTCVendor advisory
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 05:58 UTCEG score recompute
  28. 2026-08-09 05:58 UTCVendor advisory
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 04:48 UTCEG score recompute
  31. 2026-08-08 04:48 UTCVendor advisory
  32. 2026-08-07 16:24 UTCVendor advisory
  33. 2026-08-06 18:46 UTCEG score recompute
  34. 2026-08-06 18:46 UTCVendor advisory
  35. 2026-08-06 13:46 UTCEPSS rescore
  36. 2026-08-06 00:51 UTCEG score recompute
  37. 2026-08-06 00:51 UTCVendor advisory
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:38 UTCEPSS rescore
  41. 2026-08-04 02:11 UTCVendor advisory
  42. 2026-08-03 13:43 UTCEG score recompute
  43. 2026-08-03 13:43 UTCVendor advisory
  44. 2026-08-03 12:49 UTCEG score recompute
  45. 2026-08-03 12:49 UTCVendor advisory
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-02 15:22 UTCEG score recompute
  48. 2026-08-02 15:22 UTCVendor advisory
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-27 14:13 UTCEPSS rescore
  54. 2026-07-27 13:31 UTCEG score recompute
  55. 2026-07-27 13:31 UTCVendor advisory
  56. 2026-07-27 12:41 UTCEG score recompute
  57. 2026-07-27 12:41 UTCVendor advisory
  58. 2026-07-26 14:54 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-25 14:18 UTCEPSS rescore
  61. 2026-07-25 14:18 UTCEPSS rescore
  62. 2026-07-24 14:17 UTCEPSS rescore
  63. 2026-07-24 14:17 UTCEPSS rescore
  64. 2026-07-23 14:18 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 03:09 UTCEG score recompute
  67. 2026-07-22 14:08 UTCEPSS rescore
  68. 2026-07-21 15:24 UTCEPSS rescore
  69. 2026-07-20 17:08 UTCEPSS rescore
  70. 2026-07-19 14:31 UTCEPSS rescore
  71. 2026-07-19 02:29 UTCEPSS rescore
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-17 05:24 UTCOSV refresh
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-33487?
CVE-2026-33487 is a high vulnerability published on March 26, 2026. 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,…
When was CVE-2026-33487 disclosed?
CVE-2026-33487 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33487 actively exploited?
CVE-2026-33487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.1% of all scored CVEs.
What is the CVSS score of CVE-2026-33487?
CVE-2026-33487 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33487?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33487, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33487

Explore →

Is Your Infrastructure Affected by CVE-2026-33487?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs