How severe is GHSA-jcxm-7wvp-g6p5?

No CVSS score has been assigned to GHSA-jcxm-7wvp-g6p5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jcxm-7wvp-g6p5?

GHSA-jcxm-7wvp-g6p5 affects the following packages: @solana/web3.js (npm). Ecosystems affected: npm.

How do I fix GHSA-jcxm-7wvp-g6p5?

Update @solana/web3.js to 1.95.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcxm-7wvp-g6p5 is resolved across your whole dependency graph.

How do I detect GHSA-jcxm-7wvp-g6p5 in my npm dependencies?

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

How do I mitigate GHSA-jcxm-7wvp-g6p5 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-jcxm-7wvp-g6p5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jcxm-7wvp-g6p5 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-jcxm-7wvp-g6p5?

GHSA-jcxm-7wvp-g6p5 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 46th 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-jcxm-7wvp-g6p5?

GHSA-jcxm-7wvp-g6p5 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jcxm-7wvp-g6p5 published, and has it been updated?

GHSA-jcxm-7wvp-g6p5 was published on December 4, 2024 and was last updated on February 3, 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

Modified package published to npm, containing malware that exfiltrates private key materialGHSA-jcxm-7wvp-g6p5

GHSA-jcxm-7wvp-g6p5 is a Information Exposure vulnerability in @solana/web3.js. A fix is available for @solana/web3.js — see the affected versions and patch details below.

Also known asCVE-2024-54134

Published

Dec 4, 2024

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 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-jcxm-7wvp-g6p5.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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.

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

@solana/web3.jsnpm

3.5Mdownloads / week

Description

Earlier today, a publish-access account was compromised for @solana/web3.js, a JavaScript library that is commonly used by Solana dapps. This allowed an attacker to publish unauthorized and malicious packages that were modified, allowing them to steal private key material and drain funds from dapps, like bots, that handle private keys directly. This issue should not affect non-custodial wallets, as they generally do not expose private keys during transactions. This is not an issue with the Solana protocol itself, but with a specific JavaScript client library and only appears to affect projects that directly handle private keys and that updated within the window of 3:20pm UTC and 8:25pm UTC on Tuesday, December 3, 2024.

These two unauthorized versions (1.95.6 and 1.95.7) were caught within hours and have since been unpublished.

We are asking all Solana app developers to upgrade to version 1.95.8. Developers pinned to latest should also upgrade to 1.95.8.

Developers that suspect they might be compromised should rotate any suspect authority keys, including multisigs, program authorities, server keypairs, and so on.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@solana/web3.js`	≥ 1.95.6&&< 1.95.8	1.95.8`npm install @solana/web3.js@1.95.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @solana/web3.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @solana/web3.js to 1.95.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jcxm-7wvp-g6p5 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Earlier today, a publish-access account was compromised for `@solana/web3.js`, a JavaScript library that is commonly used by Solana dapps. This allowed an attacker to publish unauthorized and malicious packages that were modified, allowing them to steal private key material and drain funds from dapps, like bots, that handle private keys directly. This issue should not affect non-custodial wallets, as they generally do not expose private keys during transactions. This is not an issue with the Solana protocol itself, but with a specific JavaScript client library and only appears to affect projec

O3 Security · Impact-Aware SCA

Is GHSA-jcxm-7wvp-g6p5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works