deepmerge through 4.3.1 contains a prototype poisoning vulnerability in the mergeObject() function that fails to properly validate keys being written to target objects. Attackers can supply malicious source objects in merge operations to inject attacker-controlled properties into the returned object's prototype, causing applications to inherit unintended values when accessing properties without own-property checks.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-93753 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
This CVE ID has been rejected because it does not describe a security vulnerability.
CVE-2026-93753
✕ Withdrawn — historical dataHIGHPre-NVD 7.5
7.5CVSS
- CVSS v3
- 7.5
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
September 18, 2026
Last Modified
September 24, 2026
Frequently asked(4)
What is CVE-2026-93753?
CVE-2026-93753 is a rejected CVE ID: its record was withdrawn on November 2, 2026 and no longer describes a vulnerability. Reason given: This CVE ID has been rejected because it does not describe a security vulnerability.
When was the CVE record for CVE-2026-93753 published?
The CVE record for CVE-2026-93753 was published on September 18, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-93753?
CVE-2026-93753 has a CVSS base score of 7.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-93753?
There is nothing to remediate under CVE-2026-93753: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability.