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.
CVE-2026-73645
This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.6
- EG Score
- 6.6(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity66% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 14, 2026
Advisory Details (4)
Auto-updated Aug 13, 2026ERC7984ERC20Wrapper: once a wrapper is filled, subsequent wrap requests do not revert and result in loss of funds. · Advisory · OpenZeppelin/openzeppelin-confidential-contracts · GitHub
https://github.com/OpenZeppelin/openzeppelin-confidential-contracts/security/advisories/GHSA-hqf9-8xv5-x8xwRelease v0.3.1 (OpenZeppelin/openzeppelin-confidential-contracts)
Patch available: OpenZeppelin/openzeppelin-confidential-contracts v0.3.1
https://github.com/OpenZeppelin/openzeppelin-confidential-contracts/releases/tag/v0.3.1Revert when wrapper is full (#268)
Patch available: OpenZeppelin/openzeppelin-confidential-contracts v0.3.1 (PR #271 merged 2025-12-12)
https://github.com/OpenZeppelin/openzeppelin-confidential-contracts/pull/271commit c620d4386021 (OpenZeppelin/openzeppelin-confidential-contracts)
Patch available: OpenZeppelin/openzeppelin-confidential-contracts v0.3.1 (contains commit c620d4386021)
https://github.com/OpenZeppelin/openzeppelin-confidential-contracts/commit/c620d4386021dde63ae3ea1507dee8543791134aVendor Advisories for CVE-2026-73645(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @openzeppelin/confidential-contracts | — | 0.3.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 28× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 02:14 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:38 UTCEG score recompute
- 2026-08-23 00:27 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:50 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 23:13 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 22:38 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:02 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 21:23 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:48 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 20:12 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 19:36 UTCEG score recompute
- 2026-08-14 18:34 UTCEG score recompute
Show 3 moreShow fewer
- 2026-08-13 18:18 UTCEG score recompute
- 2026-08-13 18:12 UTCEG score recompute
- 2026-08-13 18:11 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-73645?
When was CVE-2026-73645 disclosed?
Is CVE-2026-73645 actively exploited?
What is the CVSS score of CVE-2026-73645?
How do I remediate CVE-2026-73645?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73645
Is Your Infrastructure Affected by CVE-2026-73645?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.