CVE-2025-63703
Prototype pollution in parse-ini v1.0.6 via index.js() enabling object prototype tampering.
Is CVE-2025-63703 being exploited?
Not confirmed. CVE-2025-63703 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2025-63703?
CVE-2025-63703 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-63703?
Not known from our data. No patch reference has been recorded for CVE-2025-63703, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-63703 affect?
CVE-2025-63703 affects parse-ini v1.0.6, Node.js apps using parse-ini to parse INI files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-63703?
Upgrade to patched version when released; audit dependencies
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Pollutes Object.prototype via crafted input; can enable property overwrites, data tampering, or code execution in unsafe Node.js apps.
Patch when possible