Vulnerability in @openzeppelin/confidential-contracts (CVE-2026-73645)
Summary
Vulnerability in @openzeppelin/confidential-contracts (CVE-2026-73645). Risk of unauthorized operations or information disclosure. Exploitable via ERC7984. Mitigation: upgrade to 0.3.1 or later.
Original description
The description as published by the source.
OpenZeppelin Confidential Contracts is an experimental library for developing applications on the Zama fhEVM. Prior to 0.3.1, the ERC7984 contract tracked confidential total supply with an euint64 value, and an overflowing internal _mint operation could fail silently. The wrap and onTransferReceived functions in contracts/token/ERC7984/extensions/ERC7984ERC20Wrapper.sol did not handle that failure, so a user could transfer the underlying token without receiving the corresponding confidential wrapped token. With the default rate(), the wrapper fills after approximately 18.4 trillion tokens, and subsequent wrapping requests can cause loss of funds. This issue is fixed in version 0.3.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73645 has been found in @openzeppelin/confidential-contracts.
Attackers can target a specific entry point like ERC7984 over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @openzeppelin/confidential-contracts to 0.3.1 or later.
If unsure, ask your IT team or search "@openzeppelin/confidential-contracts CVE-2026-73645" on the vendor's site.
CVE-2026-73645 (@openzeppelin/confidential-contracts) — CWE-190
Attack surface: ERC7984 / euint64 / _mint / wrap
Patched: 0.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-190) exists in @openzeppelin/confidential-contracts. Attackers reach the vulnerable code path via ERC7984.
Check the vendor advisory for the affected versions of @openzeppelin/confidential-contracts. Attack surface: ERC7984 / euint64 / _mint / wrap.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@openzeppelin/confidential-contracts' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@openzeppelin/confidential-contracts' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@openzeppelin/confidential-contractsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @openzeppelin/confidential-contracts to 0.3.1ステージング環境で 0.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com