How severe is GHSA-7j52-6fjp-58gr?

No CVSS score has been assigned to GHSA-7j52-6fjp-58gr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7j52-6fjp-58gr?

GHSA-7j52-6fjp-58gr affects the following packages: @openzeppelin/contracts-upgradeable (npm). Ecosystems affected: npm.

How do I fix GHSA-7j52-6fjp-58gr?

Update @openzeppelin/contracts-upgradeable to 4.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7j52-6fjp-58gr is resolved across your whole dependency graph.

How do I detect GHSA-7j52-6fjp-58gr in my npm dependencies?

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

How do I mitigate GHSA-7j52-6fjp-58gr 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-7j52-6fjp-58gr actively exploited in the wild?

No public exploit code has been indexed for GHSA-7j52-6fjp-58gr 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-7j52-6fjp-58gr published, and has it been updated?

GHSA-7j52-6fjp-58gr was published on March 14, 2022. 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

Inconsistent storage layout for ERC2771ContextUpgradeableGHSA-7j52-6fjp-58gr

Fix: OpenZeppelin/openzeppelin-transpiler#86

GHSA-7j52-6fjp-58gr is a security vulnerability in @openzeppelin/contracts-upgradeable. A fix is available for @openzeppelin/contracts-upgradeable — see the affected versions and patch details below.

Published

Mar 14, 2022

Updated

Mar 14, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 14, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

@openzeppelin/contracts-upgradeablenpm

434Kdownloads / week

Description

Impact

The storage layout of the ERC2771ContextUpgradeable is not constant between versions.

versions 4.0.0, 4.1.0 and 4.2.0, the contract has a length of 51 slots.
since 4.3.0, the contract has a length of 50 slots
future versions will continue using 50 slots.

This difference in layout could result in breaking upgrades if someone upgrades from an affected version to a non-affected version. It is thus recommended to be extremely careful when upgrading from a contract that uses ERC2771ContextUpgradeable <4.3.0 to a newer version that uses >=4.3.0.

We've assessed the instances of this contract found on chain (with publicly verified source code) and notified the corresponding teams of the risk that an upgrade could cause.

Workarounds

Potentially breaking upgrades would be caught by the OpenZeppelin Upgrades Plugins for Hardhat and Truffle. It is recommended to use this tooling for all your upgrades.

If you need to upgrade to a newer version of the Upgradeable Contracts library, we recommend copying the previous implementation ERC2771ContextUpgradeable (available in the release-4.2 branch) and packaging it with your code.

Reference

https://github.com/OpenZeppelin/openzeppelin-transpiler/pull/86

For more information

If you have any questions, comments, or need assistance regarding this advisory, email us at [email protected].

To submit security reports please use our bug bounty on Immunefi.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openzeppelin/contracts-upgradeable`	≥ 4.0.0&&< 4.3.0	4.3.0`npm install @openzeppelin/contracts-upgradeable@4.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openzeppelin/contracts-upgradeable, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openzeppelin/contracts-upgradeable to 4.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7j52-6fjp-58gr 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 The storage layout of the ERC2771ContextUpgradeable is not constant between versions. - versions `4.0.0`, `4.1.0` and `4.2.0`, the contract has a length of 51 slots. - since `4.3.0`, the contract has a length of 50 slots - future versions will continue using 50 slots. This difference in layout could result in breaking upgrades if someone upgrades from an affected version to a non-affected version. It is thus recommended to be extremely careful when upgrading from a contract that uses ERC2771ContextUpgradeable `<4.3.0` to a newer version that uses `>=4.3.0`. We've assessed the

O3 Security · Impact-Aware SCA

Is GHSA-7j52-6fjp-58gr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works