How severe is GHSA-xrmp-99wj-p6jc?

GHSA-xrmp-99wj-p6jc has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xrmp-99wj-p6jc?

GHSA-xrmp-99wj-p6jc affects the following packages: deap (npm). Ecosystems affected: npm.

How do I fix GHSA-xrmp-99wj-p6jc?

Update deap to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xrmp-99wj-p6jc is resolved across your whole dependency graph.

How do I detect GHSA-xrmp-99wj-p6jc in my npm dependencies?

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

How do I mitigate GHSA-xrmp-99wj-p6jc 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-xrmp-99wj-p6jc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xrmp-99wj-p6jc can be triaged on real exposure rather than presence alone.

Is GHSA-xrmp-99wj-p6jc actively exploited in the wild?

No public exploit code has been indexed for GHSA-xrmp-99wj-p6jc 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-xrmp-99wj-p6jc published, and has it been updated?

GHSA-xrmp-99wj-p6jc was published on May 31, 2019 and was last updated on August 4, 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

HIGH severity

GHSA-xrmp-99wj-p6jc — deap

HIGH

GHSA-xrmp-99wj-p6jc is a high-severity (CVSS 7.3) vulnerability in deap. A fix is available for deap — see the affected versions and patch details below.

Prototype Pollution in deap

Published

May 31, 2019

Updated

Aug 4, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 4, 2021 · 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.

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

deapnpm

75Kdownloads / week

Description

Versions of deap before 1.0.1 are vulnerable to prototype pollution.

Recommendation

Update to version 1.0.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`deap`	all versions	1.0.1`npm install deap@1.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for deap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update deap to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xrmp-99wj-p6jc 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-xrmp-99wj-p6jc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xrmp-99wj-p6jc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `deap` before 1.0.1 are vulnerable to prototype pollution. ## Recommendation Update to version 1.0.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-xrmp-99wj-p6jc in your dependencies?

O3 Security finds GHSA-xrmp-99wj-p6jc 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