ERC1155Supply vulnerability in OpenZeppelin Contracts
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@openzeppelin/contracts 4.3.3; @openzeppelin/contracts-upgradeable 4.3.3), 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.
Affected packages
- Affected
- >= 4.2.0, < 4.3.3
- Fixed in
- 4.3.3
npm @openzeppelin/contracts-upgradeable
- Affected
- >= 4.2.0, < 4.3.3
- Fixed in
- 4.3.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-wmpv-c2jp-j2xg lists affected ranges: npm @openzeppelin/contracts >=4.2.0 =4.2.0 <4.3.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-wmpv-c2jp-j2xg lists affected ranges: npm @openzeppelin/contracts >=4.2.0 =4.2.0 <4.3.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
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.
When ERC1155 tokens are minted, a callback is invoked on the receiver of those tokens, as required by the spec. When including the ERC1155Supply extension, total supply is not updated until after the callback, thus during the callback the reported total supply is lower than the real number of tokens in circulation. Impact If a system relies on accurately reported supply, an attacker may be able to mint tokens and invoke that system after receiving the token balance but before the supply is updated. Patches A fix is included in version 4.3.3 of @openzeppelin/contracts and @openzeppelin/contracts-upgradeable. Workarounds If accurate supply is relevant, do not mint tokens to untrusted receivers. Credits The issue was identified and reported by @ChainSecurityAudits. For more information Read TotalSupply Inconsistency in ERC1155 NFT Tokens by @ChainSecurityAudits for a more detailed breakdown. If you have any questions or comments about this advisory, email us at security@openzeppelin.com.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-wmpv-c2jp-j2xg
- Revision 1 · created ·
Published from osv record GHSA-wmpv-c2jp-j2xg
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-wmpv-c2jp-j2xg Advisory: ERC1155Supply vulnerability in OpenZeppelin Contracts IDs: GHSA-wmpv-c2jp-j2xg Record: https://patchnext.com/advisories/ghsa-wmpv-c2jp-j2xg (revision 2, source checked 26 Oct 2026, 12:15 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: @openzeppelin/contracts 4.3.3; @openzeppelin/contracts-upgradeable 4.3.3. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @openzeppelin/contracts: affected >= 4.2.0, < 4.3.3; fixed in 4.3.3 - npm @openzeppelin/contracts-upgradeable: affected >= 4.2.0, < 4.3.3; fixed in 4.3.3 ## Suggested inspection (read-only) - `npm ls @openzeppelin/contracts --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - `npm ls @openzeppelin/contracts-upgradeable --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 @openzeppelin/contracts, @openzeppelin/contracts-upgradeable. - 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-wmpv-c2jp-j2xg (OSV record GHSA-wmpv-c2jp-j2xg lists affected ranges: npm @openzeppelin/contracts >=4.2.0 =4.2.0 <4.3.3 (fixed)) - Verified: https://github.com/advisories/GHSA-wmpv-c2jp-j2xg (GitHub-reviewed advisory GHSA-wmpv-c2jp-j2xg lists affected ranges: npm @openzeppelin/contracts >=4.2.0 =4.2.0 <4.3.3) Commands are suggestions: review each one before running it.
Loading voting…