How severe is GHSA-7cgc-fjv4-52x6?

No CVSS score has been assigned to GHSA-7cgc-fjv4-52x6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7cgc-fjv4-52x6?

GHSA-7cgc-fjv4-52x6 affects the following packages: bignum (npm). Ecosystems affected: npm.

How do I fix GHSA-7cgc-fjv4-52x6?

Update bignum to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cgc-fjv4-52x6 is resolved across your whole dependency graph.

How do I detect GHSA-7cgc-fjv4-52x6 in my npm dependencies?

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

How do I mitigate GHSA-7cgc-fjv4-52x6 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.

How does O3 Security protect against GHSA-7cgc-fjv4-52x6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7cgc-fjv4-52x6 can be triaged on real exposure rather than presence alone.

Is GHSA-7cgc-fjv4-52x6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7cgc-fjv4-52x6 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-7cgc-fjv4-52x6 published, and has it been updated?

GHSA-7cgc-fjv4-52x6 was published on May 24, 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

GHSA-7cgc-fjv4-52x6 — bignum

Fix: justmoon/node-bignum@57e48c3

GHSA-7cgc-fjv4-52x6 is a security vulnerability in bignum. A fix is available for bignum — see the affected versions and patch details below.

Malware in pre-build binaries of bignum

Published

May 24, 2023

Updated

May 24, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 24, 2023 · 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.

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

bignumnpm

4Kdownloads / week

Description

Impact

bignum releases from v0.12.2 to v0.13.0 (inclusive) used node-pre-gyp to optionally download pre-built binary versions of the addon. These binaries were published on a now-expired S3 bucket which has since been claimed by a malicious third party which is now serving binaries containing malware that exfiltrates data from the user's computer.

Patches

v0.13.1 does not use node-pre-gyp and does not have support for downloading pre-built binaries in any form, avoiding the risk of malicious downloads.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`bignum`	≥ 0.12.2&&< 0.13.1	0.13.1`npm install bignum@0.13.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bignum, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bignum to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7cgc-fjv4-52x6 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7cgc-fjv4-52x6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-7cgc-fjv4-52x6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact bignum releases from v0.12.2 to v0.13.0 (inclusive) used node-pre-gyp to optionally download pre-built binary versions of the addon. These binaries were published on a now-expired S3 bucket which has since been claimed by a malicious third party which is now serving binaries containing malware that exfiltrates data from the user's computer. ### Patches v0.13.1 does not use node-pre-gyp and does not have support for downloading pre-built binaries in any form, avoiding the risk of malicious downloads.

O3 Security · Impact-Aware SCA

Is GHSA-7cgc-fjv4-52x6 in your dependencies?

O3 Security finds GHSA-7cgc-fjv4-52x6 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works