How severe is GHSA-29h2-jr22-frmh?

No CVSS score has been assigned to GHSA-29h2-jr22-frmh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-29h2-jr22-frmh?

GHSA-29h2-jr22-frmh affects the following packages: @openzeppelin/confidential-contracts (npm), @openzeppelin/confidential-contracts (npm), @openzeppelin/confidential-contracts (npm). Ecosystems affected: npm.

How do I fix GHSA-29h2-jr22-frmh?

Update @openzeppelin/confidential-contracts to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29h2-jr22-frmh is resolved across your whole dependency graph.

How do I detect GHSA-29h2-jr22-frmh in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openzeppelin/confidential-contracts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-29h2-jr22-frmh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-29h2-jr22-frmh actively exploited in the wild?

No public exploit code has been indexed for GHSA-29h2-jr22-frmh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-29h2-jr22-frmh published, and has it been updated?

GHSA-29h2-jr22-frmh was published on September 25, 2026 and was last updated on September 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

OpenZeppelin Confidential Contracts `VestingWalletConfidential`: a malicious ERC-7984 token is able to extract private data from the vesting walletGHSA-29h2-jr22-frmh

Fix: OpenZeppelin/openzeppelin-confidential-contracts#423

GHSA-29h2-jr22-frmh is a security vulnerability in @openzeppelin/confidential-contracts. A fix is available for @openzeppelin/confidential-contracts — see the affected versions and patch details below.

Published

Sep 25, 2026

Updated

Sep 25, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@openzeppelin/confidential-contractsnpm

1Kdownloads / week

Description

Impact

Two locations consume an encrypted handle returned by an untrusted external party and use it without verifying that the party is ACL-authorized on it.

`VestingWalletConfidential`

Malicious users can call release with a malicious token. This token could return an alternative handle on confidentialBalanceOf, which represents the balance of the vesting wallet on an alternative ERC-7984 token (or any other handle that the vesting wallet has access to). The vesting wallet does not check that the token has ACL access and grants access to a new handle derived from the returned handle.

Effectively, this bug allows a malicious user to gain information about any private euint64 handle that the vesting wallet has access to via a malicious ERC-7984 token. There is no loss of funds.

ERC7984

On a transfer with callback, ERC7984 uses the ebool returned by the recipient's IERC7984Receiver.onConfidentialTransferReceived to drive the refund logic, without checking that the recipient has ACL access to it. A malicious recipient can return any ebool the token has access to and recover its plaintext from the refund result, which the token grants the caller access to. The leak is limited to ebool handles (the value is only used as an FHE.select condition), and there is no loss of funds.

Patches

Both issues were fixed in the same patch releases: v0.5.2, v0.4.2, v0.3.2

VestingWalletConfidential: 93e75ceed2b9648f53f9d133f431064353456805 (#423).
ERC7984 transfer callback: fe0863af2c9dce7614acce98720a913bf6a767a5 (#428), with follow-up ee47edf189ab681cebdad18bfb53dee541987be2 (#431) permitting an uninitialized returned handle.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openzeppelin/confidential-contracts`	all versions	0.3.2`npm install @openzeppelin/confidential-contracts@0.3.2`
📦npm	`@openzeppelin/confidential-contracts`	≥ 0.4.0-rc.0&&< 0.4.2	0.4.2`npm install @openzeppelin/confidential-contracts@0.4.2`
📦npm	`@openzeppelin/confidential-contracts`	≥ 0.5.0-rc.0&&< 0.5.2	0.5.2`npm install @openzeppelin/confidential-contracts@0.5.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openzeppelin/confidential-contracts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openzeppelin/confidential-contracts to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29h2-jr22-frmh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Two locations consume an encrypted handle returned by an untrusted external party and use it without verifying that the party is ACL-authorized on it. #### `VestingWalletConfidential` Malicious users can call `release` with a malicious token. This token could return an alternative handle on `confidentialBalanceOf`, which represents the balance of the vesting wallet on an alternative ERC-7984 token (or any other handle that the vesting wallet has access to). The vesting wallet does not check that the token has ACL access and grants access to a new handle derived from the returned

O3 Security · Impact-Aware SCA

Is GHSA-29h2-jr22-frmh in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works