How severe is GHSA-84p7-fh9c-6g8h?

No CVSS score has been assigned to GHSA-84p7-fh9c-6g8h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-84p7-fh9c-6g8h?

GHSA-84p7-fh9c-6g8h affects the following packages: mixme (npm). Ecosystems affected: npm.

How do I fix GHSA-84p7-fh9c-6g8h?

Update mixme to 0.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84p7-fh9c-6g8h is resolved across your whole dependency graph.

How do I detect GHSA-84p7-fh9c-6g8h in my npm dependencies?

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

How do I mitigate GHSA-84p7-fh9c-6g8h 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-84p7-fh9c-6g8h actively exploited in the wild?

No public exploit code has been indexed for GHSA-84p7-fh9c-6g8h 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-84p7-fh9c-6g8h published, and has it been updated?

GHSA-84p7-fh9c-6g8h was published on September 20, 2021 and was last updated on September 16, 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

Prototype Pollution in mixmeGHSA-84p7-fh9c-6g8h

Fix: adaltas/node-mixme@db70fe9

GHSA-84p7-fh9c-6g8h is a security vulnerability in mixme. A fix is available for mixme — see the affected versions and patch details below.

Published

Sep 20, 2021

Updated

Sep 16, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 16, 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

mixmenpm

1.4Mdownloads / week

Description

Impact

When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.

Patches

The problem was patch with a more agressive discovery of secured properties to filter out.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mixme`	all versions	0.5.2`npm install mixme@0.5.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mixme, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mixme to 0.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84p7-fh9c-6g8h 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.

Frequently Asked Questions

### Impact When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content. ### Patches The problem was patch with a more agressive discovery of secured properties to filter out.

O3 Security · Impact-Aware SCA

Is GHSA-84p7-fh9c-6g8h in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works