How severe is GHSA-vjvw-wcmw-pr26?

No CVSS score has been assigned to GHSA-vjvw-wcmw-pr26 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vjvw-wcmw-pr26?

GHSA-vjvw-wcmw-pr26 affects the following packages: parsel (npm). Ecosystems affected: npm.

How do I fix GHSA-vjvw-wcmw-pr26?

No patched version of parsel has shipped for GHSA-vjvw-wcmw-pr26 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-vjvw-wcmw-pr26 in my npm dependencies?

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

How do I mitigate GHSA-vjvw-wcmw-pr26 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-vjvw-wcmw-pr26 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vjvw-wcmw-pr26 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-vjvw-wcmw-pr26 published, and has it been updated?

GHSA-vjvw-wcmw-pr26 was published on September 4, 2020 and was last updated on August 31, 2020. 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

Insufficient Entropy in parselGHSA-vjvw-wcmw-pr26

GHSA-vjvw-wcmw-pr26 is a security vulnerability in parsel. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

parselnpm

35downloads / week

Description

All versions of parsel use an insecure key derivation function. The package runs keys of arbitrary lengths through one round of SHA256 hashing for key stretching. This allows for the use of keys of insufficient entropy with inappropriate key stretching.

Recommendation

The package is deprecated and will not be updated. Consider using an alternative package.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`parsel`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parsel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of parsel has shipped for GHSA-vjvw-wcmw-pr26 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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

All versions of `parsel` use an insecure key derivation function. The package runs keys of arbitrary lengths through one round of SHA256 hashing for key stretching. This allows for the use of keys of insufficient entropy with inappropriate key stretching. ## Recommendation The package is deprecated and will not be updated. Consider using an alternative package.

O3 Security · Impact-Aware SCA

Is GHSA-vjvw-wcmw-pr26 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works