# CVE-2026-73645: ERC7984ERC20Wrapper: once a wrapper is filled, subsequent wrap requests do not revert and result in loss of funds.

> An integer overflow in the confidential total supply tracking allows users to transfer underlying tokens without receiving wrapped tokens, resulting in loss of funds.

- **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-hqf9-8xv5-x8xw

## What is CVE-2026-73645?

CVE-2026-73645 is a medium-severity vulnerability in openzeppelin-confidential-contracts, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-73645?

2 open source packages ship an affected version, including @openzeppelin/confidential-contracts.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@openzeppelin/confidential-contracts` | npm | All versions | 0.3.1 |
| `@openzeppelin/confidential-contracts` | npm | All versions | 0.3.1 |

## How do I fix CVE-2026-73645?

Upgrade @openzeppelin/confidential-contracts to 0.3.1 or later.

## Is CVE-2026-73645 being exploited?

There is no known exploitation of CVE-2026-73645 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73645 and fix it if it is affected.

What it is: CVE-2026-73645 is a medium-severity vulnerability in openzeppelin-confidential-contracts, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73645 in the wild and no public exploit code.

Affected packages and fixed versions:
- @openzeppelin/confidential-contracts (npm): affected all versions; fixed in 0.3.1
- @openzeppelin/confidential-contracts (npm): affected all versions; fixed in 0.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73645/ (Markdown: https://insights.sbomify.com/CVE-2026-73645/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73645
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73645
- OSV: https://osv.dev/vulnerability/CVE-2026-73645

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73645/
Summaries are generated and may contain mistakes; the official description above is the record.