Candy Machine Set Collection During Mint Missing Check

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.

A problem with Candy Machine V2 allow minting NFTs to an arbitrary collection due to a missing check. Here is a description of the exploit: Details: Here is the tx/ix to exploit: Transaction: Ix 1: candymachine v2, mintnft, passing in empty metadata -1 Ix 2: custom handler, 0 cpi A -- tokenmetadata createmetadataaccount, creates NFT cpi B -- candymachine v2, setcollectionduringmint Ix 1 passes our first check for empty metadata, but eventually will hit a bot tax and return Ok. We do have a CPI check in this function but even if we hit that or moved it to the top, it returns Ok as a bot tax and still enables the issue. Ix 2, cpi A is Ok and mints an arbitrary NFT. Ix 2, cpi B checks the previous instruction using indexrelativetocurrent-1. This turns out to be Ix 1 which was Ok, so then your newly minted arbitrary NFT is successfully added to the collection. Conclusion: Candy machine could be out of NFTs and it still works. If the CM is closed, (we think?) it doesn't get to the check.…

Published by the source

12 Dec 2022, 22:03 UTC

Last modified by the source

13 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:33 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9v25-r5q2-2p6w

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

# Patch Next advisory brief: GHSA-9v25-r5q2-2p6w

Advisory: Candy Machine Set Collection During Mint Missing Check
IDs: GHSA-9v25-r5q2-2p6w
Record: https://patchnext.com/advisories/ghsa-9v25-r5q2-2p6w (revision 1, source checked 26 Oct 2026, 15:33 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: mpl-candy-machine 4.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io mpl-candy-machine: affected >= 4.5.0, <= 4.5.0; fixed in 4.5.1

## Suggested inspection (read-only)
- crates.io mpl-candy-machine: 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 mpl-candy-machine.
- 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-9v25-r5q2-2p6w (GitHub-reviewed advisory GHSA-9v25-r5q2-2p6w lists affected ranges: crates.io mpl-candy-machine >=4.5.0 <=4.5.0)

Commands are suggestions: review each one before running it.