How severe is GHSA-q4h9-46xg-m3x9?

No CVSS score has been assigned to GHSA-q4h9-46xg-m3x9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q4h9-46xg-m3x9?

GHSA-q4h9-46xg-m3x9 affects the following packages: @openzeppelin/contracts-upgradeable (npm). Ecosystems affected: npm.

How do I fix GHSA-q4h9-46xg-m3x9?

Update @openzeppelin/contracts-upgradeable to 4.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4h9-46xg-m3x9 is resolved across your whole dependency graph.

How do I detect GHSA-q4h9-46xg-m3x9 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-q4h9-46xg-m3x9 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-q4h9-46xg-m3x9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q4h9-46xg-m3x9 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-q4h9-46xg-m3x9 published, and has it been updated?

GHSA-q4h9-46xg-m3x9 was published on September 15, 2021 and was last updated on September 14, 2021. 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

UUPSUpgradeable vulnerability in @openzeppelin/contracts-upgradeableGHSA-q4h9-46xg-m3x9

GHSA-q4h9-46xg-m3x9 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

Sep 15, 2021

Updated

Sep 14, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 14, 2021 · 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.

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

@openzeppelin/contracts-upgradeablenpm

250Kdownloads / week

Description

Impact

Upgradeable contracts using UUPSUpgradeable may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon.

Patches

A fix is included in version 4.3.2 of @openzeppelin/contracts and @openzeppelin/contracts-upgradeable.

Workarounds

Initialize implementation contracts using UUPSUpgradeable by invoking the initializer function (usually called initialize). An example is provided in the forum.

References

A post-mortem will be published in a few days in the OpenZeppelin Forum.

For more information

If you have any questions or comments about this advisory, or need assistance executing the mitigation, email us at [email protected].

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openzeppelin/contracts-upgradeable`	≥ 4.1.0&&< 4.3.2	4.3.2`npm install @openzeppelin/contracts-upgradeable@4.3.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/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.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4h9-46xg-m3x9 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 Upgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon. ### Patches A fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`. ### Workarounds Initialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301).

O3 Security · Impact-Aware SCA

Is GHSA-q4h9-46xg-m3x9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

UUPSUpgradeable vulnerability in @openzeppelin/contracts-upgradeableGHSA-q4h9-46xg-m3x9

Real-World Exposure

Description

Impact

Patches

Workarounds

References

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-q4h9-46xg-m3x9 in your dependencies?