Improper Verification of Cryptographic Signature Affecting rancher-2.13 package, versions <2.13.3-r4


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-RANCHER213-15790057
  • published27 Mar 2026
  • disclosed26 Mar 2026

Introduced: 26 Mar 2026

NewCVE-2026-33487  (opens in a new tab)
CWE-347  (opens in a new tab)
CWE-682  (opens in a new tab)

How to fix?

Upgrade Chainguard rancher-2.13 to version 2.13.3-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rancher-2.13 package and not the rancher-2.13 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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 Base Scores

version 3.1