False-positive validity for NFT1 genesis transactions

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-2020-15131: 1.04% estimated exploitation activity in the next 30 days; percentile 63.95 (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 In the npm package named "slp-validate", versions prior to 1.2.2 are vulnerable to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification. Patches npm package "slp-validate" has been patched and is published and tagged as version 1.2.2. Workarounds Upgrade to slp-validate 1.2.2. References Package location: https://www.npmjs.com/package/slp-validate SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements Git commit hash fixing this issue: https://github.com/simpleledger/slp-validate.js/commit/3963cf914afae69084059b82483da916d97af65c Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7 For more information If you…

Published by the source

30 Jul 2020, 14:58 UTC

Last modified by the source

10 Sep 2026, 03:48 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6jmr-jfh7-xg3h

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6jmr-jfh7-xg3h

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

# Patch Next advisory brief: CVE-2020-15131

Advisory: False-positive validity for NFT1 genesis transactions
IDs: CVE-2020-15131, GHSA-6jmr-jfh7-xg3h
Record: https://patchnext.com/advisories/cve-2020-15131 (revision 2, source checked 26 Oct 2026, 12:08 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: slp-validate 1.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm slp-validate: affected < 1.2.2; fixed in 1.2.2

## Suggested inspection (read-only)
- `npm ls slp-validate --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 slp-validate.
- 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-6jmr-jfh7-xg3h (OSV record GHSA-6jmr-jfh7-xg3h lists affected ranges: npm slp-validate >=0 <1.2.2 (fixed))
- Verified: https://github.com/advisories/GHSA-6jmr-jfh7-xg3h (GitHub-reviewed advisory GHSA-6jmr-jfh7-xg3h lists affected ranges: npm slp-validate >=0 <1.2.2)

Commands are suggestions: review each one before running it.