How severe is CVE-2025-63703?

CVE-2025-63703 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-63703 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-63703?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-63703 have an EU (EUVD) identifier?

Yes. CVE-2025-63703 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-209729.

When was CVE-2025-63703 published?

CVE-2025-63703 was published on 2026-05-07 and last updated on 2026-06-17.

CVE-2025-63703

CVE-2025-63703 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1321.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-209729
Weakness: CWE-1321
Published: 2026-05-07
Last modified: 2026-06-17

Description

npm package parse-ini v1.0.6 is vulnerable to Prototype Pollution in index.js().

Frequently asked questions

What is CVE-2025-63703?: npm package parse-ini v1.0.6 is vulnerable to Prototype Pollution in index.js().
How severe is CVE-2025-63703?: CVE-2025-63703 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-63703 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-63703?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-63703 have an EU (EUVD) identifier?: Yes. CVE-2025-63703 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-209729.
When was CVE-2025-63703 published?: CVE-2025-63703 was published on 2026-05-07 and last updated on 2026-06-17.

References

Other CWE-1321 (Prototype Pollution) vulnerabilities

CVE-2026-25142 — Critical (CVSS 10.0): SandboxJS is a JavaScript sandboxing library. Prior to 0.8.27, SanboxJS does not properly restrict __lookupGetter__…
CVE-2024-39008 — Critical (CVSS 10.0): robinweser fast-loops v1.1.3 was discovered to contain a prototype pollution via the function objectMergeDeep. This…
CVE-2024-38999 — Critical (CVSS 10.0): jrburke requirejs v2.3.6 was discovered to contain a prototype pollution via the function s.contexts._.configure. This…
CVE-2022-29823 — Critical (CVSS 10.0): Feather-Sequalize cleanQuery method uses insecure recursive logic to filter unsupported keys from the query object.…
CVE-2022-24760 — Critical (CVSS 10.0): Parse Server is an open source http web server backend. In versions prior to 4.10.7 there is a Remote Code Execution…
CVE-2020-12079 — Critical (CVSS 10.0): Beaker before 0.8.9 allows a sandbox escape, enabling system access and code execution. This occurs because Electron…

Browse all CWE-1321 (Prototype Pollution) vulnerabilities →