Skip to content
Fencer Intel
high 8.8

CVE-2018-3719 json

Prototype Pollution in mixin-deep

published 2018-06-07 8 y ago modified 2026-06-17 4 mo ago also GHSA-3mpr-hq3p-49h9 , EUVD-2018-0215

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

mixin-deep node module before 1.3.1 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.

Patch / fix

  • npm mixin-deep 1.3.1
  • mixin-deep_project mixin-deep 1.3.1
  • node-mixin-deep Debian 14, Debian 13, Debian 12 1.1.3-2

debian advisories DEBIAN-CVE-2018-3719

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-3719 updated cvss 3.3

nodejs-mixin-deep: Prototype pollution via merging functions

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.09% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/311236 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm mixin-deep
<1.3.1
1.3.1

Affected products

  • HackerOne mixin-deep node module

Classification

Weakness
  • CWE-471 Modification of Assumed-Immutable Data (MAID)
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.