How severe is GHSA-8pf3-6fgr-3g3g?

GHSA-8pf3-6fgr-3g3g has a CVSS score of 5.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8pf3-6fgr-3g3g?

GHSA-8pf3-6fgr-3g3g affects the following packages: @web3-react/coinbase-wallet (npm), @web3-react/eip1193 (npm), @web3-react/metamask (npm), @web3-react/walletconnect (npm). Ecosystems affected: npm.

How do I fix GHSA-8pf3-6fgr-3g3g?

Update @web3-react/coinbase-wallet to 8.0.35-beta.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8pf3-6fgr-3g3g is resolved across your whole dependency graph.

How do I detect GHSA-8pf3-6fgr-3g3g in my npm dependencies?

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

How do I mitigate GHSA-8pf3-6fgr-3g3g 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-8pf3-6fgr-3g3g actively exploited in the wild?

No public exploit code has been indexed for GHSA-8pf3-6fgr-3g3g 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.

What is the EPSS score for GHSA-8pf3-6fgr-3g3g?

GHSA-8pf3-6fgr-3g3g has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8pf3-6fgr-3g3g?

GHSA-8pf3-6fgr-3g3g is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8pf3-6fgr-3g3g published, and has it been updated?

GHSA-8pf3-6fgr-3g3g was published on April 18, 2023 and was last updated on November 8, 2023. 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

MEDIUM severity

`chainId` may be outdated if user changes chains as part of connection in @web3-reactGHSA-8pf3-6fgr-3g3g

MEDIUMFix: Uniswap/web3-react#749

GHSA-8pf3-6fgr-3g3g is a medium-severity (CVSS 5.2) CWE-362 vulnerability in @web3-react/coinbase-wallet. A fix is available for @web3-react/coinbase-wallet — see the affected versions and patch details below.

Also known asCVE-2023-30543

Published

Apr 18, 2023

Updated

Nov 8, 2023

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8pf3-6fgr-3g3g.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

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

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

@web3-react/coinbase-walletnpm

4Kdownloads / week

@web3-react/eip1193npm

4Kdownloads / week

@web3-react/metamasknpm

6Kdownloads / week

Description

Impact

chainId may be outdated if the user changes chains as part of the connection flow. This means that the value of chainId returned by useWeb3React() may be incorrect. In an application, this means that any data derived from chainId could be incorrect.

For example, if a swapping application derives a wrapped token contract address from the chainId and a user has changed chains as part of their connection flow the application could cause the user to send funds to the incorrect address when wrapping. This is a common approach when using other foundational libraries like ethers, and most users of v8 will want to upgrade past the affected versions.

Patches

Patched in https://github.com/Uniswap/web3-react/pull/749. Users of [email protected] should upgrade to at least:

@web3-react/coinbase-wallet@^8.0.35-beta.0
@web3-react/eip1193@^8.0.27-beta.0
@web3-react/metamask@^8.0.30-beta.0
@web3-react/walletconnect@^8.0.37-beta.0

Workarounds

N/A

References

N/A

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@web3-react/coinbase-wallet`	≥ 6.0.0&&< 8.0.35-beta.0	8.0.35-beta.0`npm install @web3-react/coinbase-wallet@8.0.35-beta.0`
📦npm	`@web3-react/eip1193`	≥ 6.0.0&&< 8.0.27-beta	8.0.27-beta`npm install @web3-react/eip1193@8.0.27-beta`
📦npm	`@web3-react/metamask`	≥ 6.0.0&&< 8.0.30-beta.0	8.0.30-beta.0`npm install @web3-react/metamask@8.0.30-beta.0`
📦npm	`@web3-react/walletconnect`	≥ 6.0.0&&< 8.0.37-beta.0	8.0.37-beta.0`npm install @web3-react/walletconnect@8.0.37-beta.0`

Affected Products

4 products · 120 configurations

Application

web3-react coinbase-walletuniswap

≥ 6.0.0 && ≤ 6.2.14

16 versions

7.0.07.0.17.0.28.0.228.0.238.0.248.0.258.0.268.0.278.0.288.0.298.0.30

Application

web3-react eip1193uniswap

≥ 6.0.0 && ≤ 6.2.14

30 versions

7.0.07.0.17.0.28.0.08.0.18.0.28.0.38.0.48.0.58.0.68.0.78.0.8

Application

web3-react metamaskuniswap

≥ 6.0.0 && ≤ 6.2.14

30 versions

8.0.08.0.18.0.28.0.38.0.48.0.58.0.68.0.78.0.88.0.98.0.108.0.11

Application

web3-react walletconnectuniswap

≥ 6.0.0 && ≤ 6.2.14

40 versions

7.0.07.0.17.0.28.0.08.0.18.0.28.0.38.0.48.0.58.0.68.0.78.0.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @web3-react/coinbase-wallet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @web3-react/coinbase-wallet to 8.0.35-beta.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8pf3-6fgr-3g3g 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 `chainId` may be outdated if the user changes chains as part of the connection flow. This means that the value of `chainId` returned by `useWeb3React()` may be incorrect. In an application, this means that any data derived from `chainId` could be incorrect. For example, if a swapping application derives a wrapped token contract address from the `chainId` *and* a user has changed chains as part of their connection flow the application could cause the user to send funds to the incorrect address when wrapping. This is a common approach when using other foundational libraries like [`et