How severe is GHSA-rx8g-88g5-qh64?

No CVSS score has been assigned to GHSA-rx8g-88g5-qh64 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rx8g-88g5-qh64?

GHSA-rx8g-88g5-qh64 affects the following packages: min-document (npm). Ecosystems affected: npm.

How do I fix GHSA-rx8g-88g5-qh64?

Update min-document to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rx8g-88g5-qh64 is resolved across your whole dependency graph.

How do I detect GHSA-rx8g-88g5-qh64 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for min-document, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rx8g-88g5-qh64 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rx8g-88g5-qh64?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rx8g-88g5-qh64 can be triaged on real exposure rather than presence alone.

Is GHSA-rx8g-88g5-qh64 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rx8g-88g5-qh64 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rx8g-88g5-qh64?

GHSA-rx8g-88g5-qh64 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rx8g-88g5-qh64?

GHSA-rx8g-88g5-qh64 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rx8g-88g5-qh64 published, and has it been updated?

GHSA-rx8g-88g5-qh64 was published on September 24, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-rx8g-88g5-qh64 — min-document

Fix: Raynos/min-document#55

GHSA-rx8g-88g5-qh64 is a CWE-1321 vulnerability in min-document. A fix is available for min-document — see the affected versions and patch details below.

min-document vulnerable to prototype pollution

Also known asCVE-2025-57352

Published

Sep 24, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rx8g-88g5-qh64.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

119other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

min-documentnpm

5.4Mdownloads / week

Description

A vulnerability exists in the 'min-document' package prior to version 2.19.0, stemming from improper handling of namespace operations in the removeAttributeNS method. By processing malicious input involving the proto property, an attacker can manipulate the prototype chain of JavaScript objects, leading to denial of service or arbitrary code execution. This issue arises from insufficient validation of attribute namespace removal operations, allowing unintended modification of critical object prototypes. The vulnerability remains unaddressed in the latest available version.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`min-document`	all versions	2.19.1`npm install min-document@2.19.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for min-document, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update min-document to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rx8g-88g5-qh64 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rx8g-88g5-qh64 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rx8g-88g5-qh64. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability exists in the 'min-document' package prior to version 2.19.1, stemming from improper handling of namespace operations in the removeAttributeNS method. By processing malicious input involving the __proto__ property, an attacker can manipulate the prototype chain of JavaScript objects, leading to denial of service or arbitrary code execution. This issue arises from insufficient validation of attribute namespace removal operations, allowing unintended modification of critical object prototypes. The vulnerability is addressed in version 2.19.1.

O3 Security · Impact-Aware SCA

Is GHSA-rx8g-88g5-qh64 in your dependencies?

O3 Security finds GHSA-rx8g-88g5-qh64 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works