What is GHSA-29H2-JR22-FRMH?

GHSA-29H2-JR22-FRMH is a high-severity security vulnerability in @openzeppelin/confidential-contracts (npm), affecting versions < 0.3.2. It is fixed in 0.3.2, 0.4.2, 0.5.2.

Which versions of @openzeppelin/confidential-contracts are affected by GHSA-29H2-JR22-FRMH?

@openzeppelin/confidential-contracts (npm) versions < 0.3.2 is affected.

Is there a fix for GHSA-29H2-JR22-FRMH?

Yes. GHSA-29H2-JR22-FRMH is fixed in 0.3.2, 0.4.2, 0.5.2. Upgrade to this version or later.

Is GHSA-29H2-JR22-FRMH exploitable, and should I be worried?

Whether GHSA-29H2-JR22-FRMH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-29H2-JR22-FRMH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-29H2-JR22-FRMH?

Upgrade: @openzeppelin/confidential-contracts to 0.3.2 or later, @openzeppelin/confidential-contracts to 0.4.2 or later, @openzeppelin/confidential-contracts to 0.5.2 or later.

GHSA-29H2-JR22-FRMH

Q: Which versions of @openzeppelin/confidential-contracts are affected by GHSA-29H2-JR22-FRMH?

@openzeppelin/confidential-contracts (npm) versions < 0.3.2 is affected.

Q: Is there a fix for GHSA-29H2-JR22-FRMH?

Yes. GHSA-29H2-JR22-FRMH is fixed in 0.3.2, 0.4.2, 0.5.2. Upgrade to this version or later.

Q: Is GHSA-29H2-JR22-FRMH exploitable, and should I be worried?

Whether GHSA-29H2-JR22-FRMH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-29H2-JR22-FRMH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-29H2-JR22-FRMH?

Upgrade: @openzeppelin/confidential-contracts to 0.3.2 or later, @openzeppelin/confidential-contracts to 0.4.2 or later, @openzeppelin/confidential-contracts to 0.5.2 or later.

Summary

OpenZeppelin Confidential Contracts VestingWalletConfidential: a malicious ERC-7984 token is able to extract private data from the vesting wallet

`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.

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.

Affected versions

@openzeppelin/confidential-contracts (< 0.3.2) @openzeppelin/confidential-contracts (>= 0.4.0-rc.0, < 0.4.2) @openzeppelin/confidential-contracts (>= 0.5.0-rc.0, < 0.5.2)

Security releases

@openzeppelin/confidential-contracts → 0.3.2 (npm) @openzeppelin/confidential-contracts → 0.4.2 (npm) @openzeppelin/confidential-contracts → 0.5.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is GHSA-29H2-JR22-FRMH? GHSA-29H2-JR22-FRMH is a high-severity security vulnerability in @openzeppelin/confidential-contracts (npm), affecting versions < 0.3.2. It is fixed in 0.3.2, 0.4.2, 0.5.2.
Which versions of @openzeppelin/confidential-contracts are affected by GHSA-29H2-JR22-FRMH? @openzeppelin/confidential-contracts (npm) versions < 0.3.2 is affected.
Is there a fix for GHSA-29H2-JR22-FRMH? Yes. GHSA-29H2-JR22-FRMH is fixed in 0.3.2, 0.4.2, 0.5.2. Upgrade to this version or later.
Is GHSA-29H2-JR22-FRMH exploitable, and should I be worried? Whether GHSA-29H2-JR22-FRMH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-29H2-JR22-FRMH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-29H2-JR22-FRMH?
- Upgrade @openzeppelin/confidential-contracts to 0.3.2 or later
- Upgrade @openzeppelin/confidential-contracts to 0.4.2 or later
- Upgrade @openzeppelin/confidential-contracts to 0.5.2 or later

Other vulnerabilities in @openzeppelin/confidential-contracts

CVE-IDSeverityPackage summary

CVE-2026-73645Medium@openzeppelin/confidential-contracts: ERC7984ERC20Wrapper: once a wrapper is filled, subsequent wrap requests do not revert and result in loss of funds.