ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-93753

sync 2026-10-27T21:35:50Z

Published Unknown date · sync 2026-10-27T21:35:50Z

Last checked Oct 28, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-93753. EPSS is 0.51%. Act only if a listed version of sync 2026-10-27T21:35:50Z is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (sync 2026-10-27T21:35:50Z).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.51%
Remediation
Version ranges on file
Affected products
npm deepmerge

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 wi

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm deepmerge>=4.2.0 <=4.3.1

How to fix CVE-2026-93753

  • Upgrade

    CVE-2026-93753 lists a fix boundary at 4.3.1. Compare the installed build with that boundary before you change production.

  • Version check

    Seen in >=4.2.0 <=4.3.1

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-93753. EPSS is 0.51%. Act only if a listed version of sync 2026-10-27T21:35:50Z is installed.

Which versions are affected?

Compare what you have installed with >=4.2.0 <=4.3.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.51%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 28, 2026 · GitLab Advisory Database

    Detected

    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 wi

Sources

  • CVE.orgVulnerability recordCVE-2026-93753

    Official CVE identifier

    cve.org
  • GitLab Advisory DatabasePackage advisorynpm/deepmerge/CVE-2026-93753.yml

    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 wi

    gitlab.com

Freshness

Last verified in this catalog Oct 28, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgOct 28, 2026
  • GitLab Advisory DatabaseOct 28, 2026