Security vulnerabilities should be disclosed to the project maintainers through Immunefi, or alternatively by email to security@openzeppelin.com.
Responsible disclosure of security vulnerabilities is rewarded through a bug bounty program on Immunefi.
There is a bonus reward for issues introduced in release candidates that are reported before making it into a stable release.
Security vulnerabilities will be patched as soon as responsibly possible, and published as an advisory on this repository (see advisories) and on the affected npm packages.
Projects that build on OpenZeppelin Contracts are encouraged to clearly state, in their source code and websites, how to be contacted about security issues in the event that a direct notification is considered necessary. We recommend including it in the NatSpec for the contract as /// @custom:security-contact security@example.com.
Additionally, we recommend installing the library through npm and setting up vulnerability alerts such as Dependabot.
Security patches will be released for the latest minor of a given major release. For example, if an issue is found in versions >=4.6.0 and the latest is 4.8.0, the patch will be released only in version 4.8.1.
Only critical severity bug fixes will be backported to past major releases.
| Version | Critical security fixes | Other security fixes |
|---|---|---|
| 4.x | ✅ | ✅ |
| 3.4 | ✅ | ❌ |
| 2.5 | ✅ | ❌ |
| < 2.0 | ❌ | ❌ |
Note as well that the Solidity language itself only guarantees security updates for the latest release.
Smart contracts are a nascent techology and carry a high level of technical risk and uncertainty. OpenZeppelin Contracts is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including OpenZeppelin. Your use of the project is also governed by the terms found at www.openzeppelin.com/tos (the "Terms"). As set out in the Terms, you are solely responsible for any use of OpenZeppelin Contracts and you assume all risks associated with any such use. This Security Policy in no way evidences or represents an on-going duty by any contributor, including OpenZeppelin, to correct any flaws or alert you to all or any of the potential risks of utilizing the project.