Solana Pay Vulnerable to Weakness in Transfer Validation Logic

Exploitation

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

CVSS

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

EPSS

• CVE-2022-35917: 0.87% estimated exploitation activity in the next 30 days; percentile 58.76 (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.

Description When a Solana Pay transaction is located using a reference key, it may be checked to represent a transfer of the desired amount to the recipient, using the supplied validateTransfer function. An edge case regarding this mechanism could cause the validation logic to validate multiple transfers. Impact Most known Solana Pay point of sale applications are currently run on physical point of sale devices, which makes this issue unlikely to occur. However, there may be web-based point of sale applications using the protocol where it may be more likely to occur. Patches This issue has been patched as of version 0.2.1. Users of the Solana Pay SDK should upgrade to it.

Published by the source

6 Aug 2022, 05:39 UTC

Last modified by the source

8 Nov 2023, 04:09 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j47c-j42c-mwqq

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j47c-j42c-mwqq

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

# Patch Next advisory brief: CVE-2022-35917

Advisory: Solana Pay Vulnerable to Weakness in Transfer Validation Logic
IDs: CVE-2022-35917, GHSA-j47c-j42c-mwqq
Record: https://patchnext.com/advisories/cve-2022-35917 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @solana/pay 0.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @solana/pay: affected <= 0.2.0; fixed in 0.2.1

## Suggested inspection (read-only)
- `npm ls @solana/pay --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 @solana/pay.
- 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-j47c-j42c-mwqq (OSV record GHSA-j47c-j42c-mwqq lists affected ranges: npm @solana/pay >=0 <0.2.1 (fixed))
- Verified: https://github.com/advisories/GHSA-j47c-j42c-mwqq (GitHub-reviewed advisory GHSA-j47c-j42c-mwqq lists affected ranges: npm @solana/pay >=0 <=0.2.0)

Commands are suggestions: review each one before running it.