VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@openzeppelin/contracts: vulnerability history, versions and safety

@openzeppelin/contracts is a package in the npm ecosystem. Vulert records 21 vulnerabilities for it across 82 releases, from Aug 2021 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded C2 H6 M11 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @openzeppelin/contracts vulnerabilities

Vulert verdict on @openzeppelin/contracts 5.6.1 i

Updated on 23 Oct 2026

Good news: 5.6.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 21.

Package health score 80/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 5.6.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.6.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.6.1 — unaffected i
  • Vulnerabilities on record 21 over 3 years · 0 in the last year i
  • Latest disclosure 17 Jul 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 1,121 packages i
  • Stars 27,288 i
  • OpenSSF scorecard 5/10 i
  • Last release 7 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @openzeppelin/contracts, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.7.0 29 Jul 2026 none MIT — Details →
5.7.0-rc.0 15 Jul 2026 none MIT — Details →
5.6.1 27 Feb 2026 none MIT — Details →
5.6.0 25 Feb 2026 none MIT — Details →
5.6.0-rc.1 12 Jan 2026 none MIT — Details →
5.6.0-rc.0 19 Dec 2025 none MIT — Details →
5.5.0 31 Oct 2025 none MIT — Details →
5.5.0-rc.1 10 Oct 2025 none MIT — Details →
5.5.0-rc.0 26 Sep 2025 none MIT — Details →
5.4.0 17 Jul 2025 none MIT — Details →
5.4.0-rc.1 20 Jun 2025 M1 MIT Yes Details →
5.4.0-rc.0 18 Jun 2025 M1 MIT Yes Details →
5.3.0 09 Apr 2025 M1 MIT Yes Details →
5.3.0-rc.0 19 Mar 2025 M1 MIT Yes Details →
5.2.0 09 Jan 2025 M1 MIT Yes Details →
5.2.0-rc.1 16 Dec 2024 none MIT — Details →
5.2.0-rc.0 04 Dec 2024 none MIT — Details →
5.1.0 17 Oct 2024 none MIT — Details →
5.1.0-rc.1 17 Oct 2024 none MIT — Details →
5.1.0-rc.0 03 Oct 2024 none MIT — Details →
4.9.6 29 Feb 2024 none MIT — Details →
5.0.2 29 Feb 2024 none MIT — Details →
4.9.5 08 Dec 2023 L1 MIT Yes Details →
5.0.1 07 Dec 2023 none MIT — Details →
4.9.4 07 Dec 2023 M1 MIT Yes Details →
5.0.0 05 Oct 2023 none MIT — Details →
5.0.0-rc.2 02 Oct 2023 none MIT — Details →
5.0.0-rc.1 28 Sep 2023 none MIT — Details →
5.0.0-rc.0 19 Sep 2023 none MIT — Details →
4.9.3 28 Jul 2023 L1 MIT Yes Details →
4.9.2 16 Jun 2023 M1 L1 MIT Yes Details →
4.9.1 07 Jun 2023 M2 L1 MIT Yes Details →
4.9.0 23 May 2023 M3 L1 MIT Yes Details →
4.9.0-rc.1 17 May 2023 M3 L1 MIT Yes Details →
4.9.0-rc.0 09 May 2023 M3 L1 MIT Yes Details →
4.8.3 13 Apr 2023 M3 L1 MIT Yes Details →
4.8.2 02 Mar 2023 H1 M4 L1 MIT Yes Details →
4.8.1 13 Jan 2023 H1 M5 L1 MIT Yes Details →
4.8.0 08 Nov 2022 H1 M5 L1 MIT Yes Details →
4.8.0-rc.2 17 Oct 2022 H1 M4 L1 MIT Yes Details →
4.8.0-rc.1 23 Sep 2022 H1 M4 L1 MIT Yes Details →
4.8.0-rc.0 07 Sep 2022 H1 M4 L1 MIT Yes Details →
4.7.3 10 Aug 2022 H1 M4 L1 MIT Yes Details →
4.7.2 27 Jul 2022 H2 M4 L1 MIT Yes Details →
4.7.1 20 Jul 2022 H3 M6 L1 MIT Yes Details →
4.7.0 29 Jun 2022 H5 M6 L1 MIT Yes Details →
4.7.0-rc.0 07 Jun 2022 H5 M5 L1 MIT Yes Details →
4.6.0 26 Apr 2022 H5 M5 L1 MIT Yes Details →
4.6.0-rc.0 31 Mar 2022 H5 M4 L1 MIT Yes Details →
4.5.0 09 Feb 2022 H5 M4 L1 MIT Yes Details →
4.5.0-rc.0 13 Jan 2022 H5 M4 MIT Yes Details →
4.4.2 11 Jan 2022 H5 M4 MIT Yes Details →
4.4.1 14 Dec 2021 H5 M5 MIT Yes Details →
4.4.0 25 Nov 2021 H6 M6 MIT Yes Details →
4.4.0-rc.1 16 Nov 2021 H6 M6 MIT Yes Details →
4.3.3 12 Nov 2021 H6 M6 MIT Yes Details →
4.4.0-rc.0 20 Oct 2021 H6 M6 MIT Yes Details →
4.3.2 14 Sep 2021 H6 M6 L1 MIT Yes Details →
3.4.2-solc-0.7 26 Aug 2021 H1 M3 MIT Yes Details →
4.3.1 26 Aug 2021 C1 H6 M6 L1 MIT Yes Details →
3.4.2 26 Aug 2021 H1 M3 MIT Yes Details →
4.3.0 17 Aug 2021 C2 H6 M6 L1 MIT Yes Details →
4.3.0-rc.0 06 Aug 2021 C2 H4 M4 L1 MIT Yes Details →
4.2.0 30 Jun 2021 C2 H4 M4 L1 MIT Yes Details →
4.2.0-rc.0 23 Jun 2021 C2 H4 M4 MIT Yes Details →
4.1.0 29 Apr 2021 C2 H4 M4 MIT Yes Details →
4.1.0-rc.0 16 Apr 2021 C1 H2 M4 MIT Yes Details →
4.0.0 23 Mar 2021 C1 H2 M4 MIT Yes Details →
4.0.0-rc.0 09 Mar 2021 H1 M3 MIT Yes Details →
3.4.1-solc-0.7-2 03 Mar 2021 H1 M3 MIT Yes Details →
3.4.1-solc-0.7 03 Mar 2021 H1 M3 MIT Yes Details →
3.4.1 03 Mar 2021 H1 M3 MIT Yes Details →
4.0.0-beta.1 03 Mar 2021 H1 M3 MIT Yes Details →
4.0.0-beta.0 22 Feb 2021 H1 M3 MIT Yes Details →
3.4.0-solc-0.7 02 Feb 2021 H1 M3 MIT Yes Details →
3.4.0 02 Feb 2021 H1 M3 MIT Yes Details →
3.4.0-rc.0 26 Jan 2021 H1 M3 MIT Yes Details →
3.3.0-solc-0.7 27 Nov 2020 H1 M3 MIT Yes Details →
3.3.0 26 Nov 2020 H1 M3 MIT Yes Details →
3.3.0-rc.2 24 Nov 2020 H1 M3 MIT Yes Details →
3.3.0-rc.1 18 Nov 2020 H1 M3 MIT Yes Details →
3.3.0-rc.0 17 Nov 2020 H1 M3 MIT Yes Details →
3.2.2-solc-0.7 28 Oct 2020 H1 M3 MIT Yes Details →
3.2.1-solc-0.7 15 Sep 2020 H1 M3 MIT Yes Details →
3.2.0-solc-0.7 11 Sep 2020 H1 M1 MIT Yes Details →
3.2.0 10 Sep 2020 H1 M3 MIT Yes Details →
3.2.0-rc.0 03 Sep 2020 H1 M1 MIT Yes Details →
3.1.0-solc-0.7 30 Jul 2020 H1 M1 MIT Yes Details →
3.1.0 23 Jun 2020 H1 M1 MIT Yes Details →
3.1.0-rc.0 11 Jun 2020 H1 M1 MIT Yes Details →
3.0.2 08 Jun 2020 H1 M1 MIT Yes Details →
3.0.1 27 Apr 2020 H1 M1 MIT Yes Details →
2.5.1 27 Apr 2020 H1 M1 MIT Yes Details →
3.0.0 20 Apr 2020 H1 M1 MIT Yes Details →
3.0.0-rc.1 03 Apr 2020 H1 M1 MIT Yes Details →
3.0.0-rc.0 16 Mar 2020 H1 M1 MIT Yes Details →
3.0.0-beta.0 14 Feb 2020 H1 M1 MIT Yes Details →
2.5.0 04 Feb 2020 H1 M1 MIT Yes Details →
2.5.0-rc.0 24 Jan 2020 H1 M1 MIT Yes Details →
2.4.0 29 Oct 2019 H1 M1 MIT Yes Details →
2.4.0-beta.2 16 Aug 2019 H1 M1 — Yes Details →
2.4.0-beta.1 16 Aug 2019 H1 M1 — Yes Details →
2.4.0-beta.0 15 Aug 2019 H1 M1 — Yes Details →
2.3.0 26 Jul 2019 H1 M1 — Yes Details →

All 104 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 4
  • 2022 8
  • 2023 7
  • 2024 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 21 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @openzeppelin/contracts

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-39167: TimelockController vulnerability in OpenZeppelin Contracts 10.0 critical 4.3.1 30 Aug 2021
CVE-2021-41264: UUPSUpgradeable vulnerability in @openzeppelin/contracts 9.8 critical 4.3.2 15 Sep 2021
CVE-2023-30542: Vulnerability in @openzeppelin/contracts package - GovernorCompatibilityBravo may trim proposal calldata 8.8 high 4.8.3 20 Apr 2023
CVE-2022-35961: OpenZeppelin Contracts vulnerable to ECDSA signature malleability 7.9 high 4.7.3 18 Aug 2022
CVE-2022-31198: OpenZeppelin Contracts's GovernorVotesQuorumFraction Vulnerability 7.5 high 4.7.2 18 Aug 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @openzeppelin/contracts

Is @openzeppelin/contracts safe to use?

Vulert records 21 vulnerabilities for @openzeppelin/contracts in npm: 2 critical, 6 high, 11 medium and 2 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @openzeppelin/contracts's Vulert package health score?

Vulert scores @openzeppelin/contracts 80/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @openzeppelin/contracts affected?

No. 5.6.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @openzeppelin/contracts should I use?

5.6.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @openzeppelin/contracts have?

21 vulnerabilities are recorded for @openzeppelin/contracts in the npm ecosystem: 2 critical, 6 high, 11 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @openzeppelin/contracts vulnerabilities disclosed?

0 vulnerabilities were recorded for @openzeppelin/contracts in the last 12 months, and the oldest entry in this database dates to 30 Aug 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @openzeppelin/contracts are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @openzeppelin/contracts for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @openzeppelin/contracts version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.