Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Holder can generate proof of ownership for credentials it does not control in vp-toolkit

GHSA-ff5x-w9wg-h275

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (vp-toolkit 0.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact The verifyVerifiablePresentation() method check the cryptographic integrity of the Verifiable Presentation, but it does not check if the credentialSubject.id DID matches the signer of the VP proof. The verifier is impacted by this vulnerability. Patches Patch will be available in version 0.2.2. Workarounds - Compute the address out of the verifiablePresentation.proof.n.verificationMethod using getAddressFromPubKey() from crypt-util@0.1.5 and match it with the credentialSubject.id address from the credential. References Github issue For more information If you have any questions or comments about this advisory: Discuss in the existing issue Contact me

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-ff5x-w9wg-h275

  2. Revision 1 · created ·

    Published from osv record GHSA-ff5x-w9wg-h275

Agent brief

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

# Patch Next advisory brief: GHSA-ff5x-w9wg-h275

Advisory: Holder can generate proof of ownership for credentials it does not control in vp-toolkit
IDs: GHSA-ff5x-w9wg-h275
Record: https://patchnext.com/advisories/ghsa-ff5x-w9wg-h275 (revision 2, source checked 26 Oct 2026, 12:07 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: Vendor fix available; fixed versions by package: vp-toolkit 0.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vp-toolkit: affected < 0.2.2; fixed in 0.2.2

## Suggested inspection (read-only)
- `npm ls vp-toolkit --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 vp-toolkit.
- 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://osv.dev/vulnerability/GHSA-ff5x-w9wg-h275 (OSV record GHSA-ff5x-w9wg-h275 lists affected ranges: npm vp-toolkit >=0 <0.2.2 (fixed))
- Verified: https://github.com/advisories/GHSA-ff5x-w9wg-h275 (GitHub-reviewed advisory GHSA-ff5x-w9wg-h275 lists affected ranges: npm vp-toolkit >=0 <0.2.2)

Commands are suggestions: review each one before running it.

Loading voting…