Predictable SIF UUID Identifiers in github.com/sylabs/sif

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2021-29499: 0.96% estimated exploitation activity in the next 30 days; percentile 61.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The siftool new command and func siftool.New() produce predictable UUID identifiers due to insecure randomness in the version of the github.com/satori/go.uuid module used as a dependency. Patches A patch is available in version = v1.2.3 of the module. Users are encouraged to upgrade. The patch is commit https://github.com/sylabs/sif/commit/193962882122abf85ff5f5bcc86404933e71c07d Workarounds Users passing CreateInfo struct should ensure the ID field is generated using a version of github.com/satori/go.uuid that is not vulnerable to this issue. Unfortunately, the latest tagged release is vulnerable to this issue. One way to obtain a non-vulnerable version is: References https://github.com/satori/go.uuid/issues/73 For more information If you have any questions or comments about this advisory: Open an issue in github.com/sylabs/sif Email us at security@sylabs.io

Published by the source

18 May 2021, 18:30 UTC

Last modified by the source

3 Feb 2023, 05:00 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4gh8-x3vv-phhg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-29499

Advisory: Predictable SIF UUID Identifiers in github.com/sylabs/sif
IDs: CVE-2021-29499, GHSA-4gh8-x3vv-phhg
Record: https://patchnext.com/advisories/cve-2021-29499 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/sylabs/sif 1.2.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/sylabs/sif: affected < 1.2.3; fixed in 1.2.3

## Suggested inspection (read-only)
- Go github.com/sylabs/sif: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/sylabs/sif.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4gh8-x3vv-phhg (GitHub-reviewed advisory GHSA-4gh8-x3vv-phhg lists affected ranges: Go github.com/sylabs/sif >=0 <1.2.3)

Commands are suggestions: review each one before running it.