Skip to main content
VulnerabilityPublished Updated

CVE-2025-57352: min-document vulnerable to prototype pollution

Affects min-documentSource GCVE Database

0
Compare
Authoritative record:CVE-2025-57352· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.19.1 when convenient.

Data as of 4 Nov 2026, 18:30 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.19.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade min-document to 2.19.1.

Affected software

ProductAffectedFixed in
npmmin-documentAffected
  • <2.19.1
Fixed in
  • 2.19.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to min-document version 2.19.1 or later, where this vulnerability is fixed. Applying this official patch fully mitigates the issue.

Description

The 'min-document' package prior to version 2.19.1 contains a prototype pollution vulnerability in the removeAttributeNS method. This flaw allows attackers to manipulate the JavaScript prototype chain by exploiting improper handling of the __proto__ property during namespace attribute removal. The vulnerability can lead to denial of service or arbitrary code execution. A fix is available in version 2.19.1.

References

Community reviews

Loading reviews…