How severe is GHSA-pv55-r6j3-wp94?

No CVSS score has been assigned to GHSA-pv55-r6j3-wp94 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pv55-r6j3-wp94?

GHSA-pv55-r6j3-wp94 affects the following packages: eslint-config-eslint (npm). Ecosystems affected: npm.

How do I fix GHSA-pv55-r6j3-wp94?

No patched version of eslint-config-eslint has shipped for GHSA-pv55-r6j3-wp94 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-pv55-r6j3-wp94 in my npm dependencies?

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

How do I mitigate GHSA-pv55-r6j3-wp94 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-pv55-r6j3-wp94 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pv55-r6j3-wp94 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-pv55-r6j3-wp94 published, and has it been updated?

GHSA-pv55-r6j3-wp94 was published on September 1, 2020 and was last updated on July 27, 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

Malicious Package in eslint-config-eslintGHSA-pv55-r6j3-wp94

GHSA-pv55-r6j3-wp94 is a security vulnerability in eslint-config-eslint. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Jul 27, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jul 27, 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.

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

eslint-config-eslintnpm

31Kdownloads / week

Description

Version 5.0.2 of eslint-config-eslint was published without authorization and was found to contain malicious code. This code would read the users .npmrc file and send any found authentication tokens to a remote server.

Recommendation

The best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens

Users may consider downgrading to version 5.0.1

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`eslint-config-eslint`	all versions	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 eslint-config-eslint, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of eslint-config-eslint has shipped for GHSA-pv55-r6j3-wp94 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

Version 5.0.2 of `eslint-config-eslint` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to a remote server. ## Recommendation The best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens Users may consider downgrading to version 5.0.1

O3 Security · Impact-Aware SCA

Is GHSA-pv55-r6j3-wp94 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works