SIF's Digital Signature Hash Algorithms Not Validated

Exploitation

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

CVSS

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

EPSS

• CVE-2022-39237: 0.65% estimated exploitation activity in the next 30 days; percentile 51.22 (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 github.com/sylabs/sif/v2/pkg/integrity package does not verify that the hash algorithm(s) used are cryptographically secure when verifying digital signatures. Patches A patch is available in version = v2.8.1 of the module. Users are encouraged to upgrade. The patch is commit https://github.com/sylabs/sif/commit/07fb86029a12e3210f6131e065570124605daeaa Workarounds Users may independently validate that the hash algorithm(s) used for metadata digest(s) and signature hash are cryptographically secure. References CVE-2004-2761 CVE-2005-4900 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

6 Oct 2022, 19:54 UTC

Last modified by the source

17 Feb 2023, 22:14 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m5m3-46gj-wch8

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

# Patch Next advisory brief: CVE-2022-39237

Advisory: SIF's Digital Signature Hash Algorithms Not Validated
IDs: CVE-2022-39237, GHSA-m5m3-46gj-wch8
Record: https://patchnext.com/advisories/cve-2022-39237 (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: Medium (CVSS 6.3)
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/v2 2.8.1. A vendor fix does not mean a deployment is fixed.

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

## Suggested inspection (read-only)
- Go github.com/sylabs/sif/v2: 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/v2.
- 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-m5m3-46gj-wch8 (GitHub-reviewed advisory GHSA-m5m3-46gj-wch8 lists affected ranges: Go github.com/sylabs/sif/v2 >=0 <2.8.1)

Commands are suggestions: review each one before running it.