slsa-verifier vulnerable to mproper validation of npm's publish attestations

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary slsa-verifier<=2.4.0 does not correctly verify npm's publish attestations signature. Proof of concept Steps to reproduce: 1. curl -Sso attestations.json $(npm view @trishankatdatadog/supreme-goggles --json | jq -r '.dist.attestations.url') 2. curl -Sso supreme-goggles.tgz "$(npm view @trishankatdatadog/supreme-goggles --json | jq -r '.dist.tarball')" 3. In attestations.json, take the value addressed by the jq selector .attestations[0].bundle.dsseEnvelope.payload, base64decode it, tamper with it, base64encode that, and replace the original value with that. Save the file as attestationstampered.json. Here is an example command to replace the package name with @attacker/malicious: jq -r ".attestations[0].bundle.dsseEnvelope.payload = \"$(jq -r '.attestations[0].bundle.dsseEnvelope.payload | @base64d' < attestations.json | jq '.subject[0].name = "pkg:npm/%40attacker/malicious"' | base64 -w0)\"" < attestations.json attestationstampered.json 5. SLSAVERIFIEREXPERIMENTAL=1…

Published by the source

8 Nov 2023, 19:15 UTC

Last modified by the source

9 Nov 2023, 16:14 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r2xv-vpr2-42m9

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

# Patch Next advisory brief: GHSA-r2xv-vpr2-42m9

Advisory: slsa-verifier vulnerable to mproper validation of npm's publish attestations
IDs: GHSA-r2xv-vpr2-42m9
Record: https://patchnext.com/advisories/ghsa-r2xv-vpr2-42m9 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/slsa-framework/slsa-verifier/v2 2.4.1-rc.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/slsa-framework/slsa-verifier/v2: affected <= 2.4.0; fixed in 2.4.1-rc.0
- Go github.com/slsa-framework/slsa-verifier: affected <= 1.4.1

## Suggested inspection (read-only)
- Go github.com/slsa-framework/slsa-verifier/v2: check the installed version with your package manager.
- Go github.com/slsa-framework/slsa-verifier: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/slsa-framework/slsa-verifier/v2, github.com/slsa-framework/slsa-verifier.
- 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-r2xv-vpr2-42m9 (GitHub-reviewed advisory GHSA-r2xv-vpr2-42m9 lists affected ranges: Go github.com/slsa-framework/slsa-verifier/v2 >=0 =0 <=1.4.1)

Commands are suggestions: review each one before running it.