How severe is GHSA-4wv4-mgfq-598v?

No CVSS score has been assigned to GHSA-4wv4-mgfq-598v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4wv4-mgfq-598v?

GHSA-4wv4-mgfq-598v affects the following packages: nobelprizeparser (npm). Ecosystems affected: npm.

How do I fix GHSA-4wv4-mgfq-598v?

Update nobelprizeparser to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4wv4-mgfq-598v is resolved across your whole dependency graph.

How do I detect GHSA-4wv4-mgfq-598v in my npm dependencies?

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

How do I mitigate GHSA-4wv4-mgfq-598v if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-4wv4-mgfq-598v actively exploited in the wild?

No public exploit code has been indexed for GHSA-4wv4-mgfq-598v 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-4wv4-mgfq-598v published, and has it been updated?

GHSA-4wv4-mgfq-598v was published on March 12, 2021 and was last updated on March 12, 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

Code injection in nobelprizeparserGHSA-4wv4-mgfq-598v

Fix: AnneTheDev/nobelprize@00639d3

GHSA-4wv4-mgfq-598v is a security vulnerability in nobelprizeparser. A fix is available for nobelprizeparser — see the affected versions and patch details below.

Published

Mar 12, 2021

Updated

Mar 12, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 12, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦nobelprizeparser

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Code injection through use of eval.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`nobelprizeparser`	all versions	1.0.2`npm install nobelprizeparser@1.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nobelprizeparser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nobelprizeparser to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4wv4-mgfq-598v is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Code injection through use of eval.

O3 Security · Impact-Aware SCA

Is GHSA-4wv4-mgfq-598v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works