Prototype Pollution in mixme
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mixme 0.5.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm mixme
- Affected
- < 0.5.2
- Fixed in
- 0.5.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-84p7-fh9c-6g8h lists affected ranges: npm mixme >=0 <0.5.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-84p7-fh9c-6g8h lists affected ranges: npm mixme >=0 <0.5.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-84p7-fh9c-6g8h
- Revision 1 · created ·
Published from osv record GHSA-84p7-fh9c-6g8h
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-84p7-fh9c-6g8h Advisory: Prototype Pollution in mixme IDs: GHSA-84p7-fh9c-6g8h Record: https://patchnext.com/advisories/ghsa-84p7-fh9c-6g8h (revision 2, source checked 26 Oct 2026, 12:15 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mixme 0.5.2. A vendor fix does not mean a deployment is fixed. ## Affected components - npm mixme: affected < 0.5.2; fixed in 0.5.2 ## Suggested inspection (read-only) - `npm ls mixme --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on mixme. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-84p7-fh9c-6g8h (OSV record GHSA-84p7-fh9c-6g8h lists affected ranges: npm mixme >=0 <0.5.2 (fixed)) - Verified: https://github.com/advisories/GHSA-84p7-fh9c-6g8h (GitHub-reviewed advisory GHSA-84p7-fh9c-6g8h lists affected ranges: npm mixme >=0 <0.5.2) Commands are suggestions: review each one before running it.
Loading voting…