Is CVE-2025-25975 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-25975 being exploited in the wild.

How severe is CVE-2025-25975?

Low severity, with a CVSS score of 3.1, published 12 March 2025.

Which products and versions are affected?

parse-git-config (npm) SEMVER:introduced=0,last_affected=3.0.0.

Is there a fix for CVE-2025-25975?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-25975 attacked?

It is attacked over the network.

Am I affected by CVE-2025-25975?

Check whether you run parse-git-config (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-25975: parse-git-config prototype pollution via expandKeys

CVE-2025-25975 · Severity: low · CVSS 3.1 · Published 2025-03-12

parse-git-config is a Node.js library used to parse Git configuration files. A prototype pollution vulnerability in the expandKeys function allows an attacker to pollute the JavaScript object prototype chain, potentially modifying behavior across an application. If the polluted properties reach sensitive APIs (like code execution functions), this could lead to arbitrary command execution or other malicious actions.

Vendors: npm.

Quick answers

Is CVE-2025-25975 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-25975 being exploited in the wild.
How severe is CVE-2025-25975?: Low severity, with a CVSS score of 3.1, published 12 March 2025.
Which products and versions are affected?: parse-git-config (npm) SEMVER:introduced=0,last_affected=3.0.0.
Is there a fix for CVE-2025-25975?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-25975 attacked?: It is attacked over the network.
Am I affected by CVE-2025-25975?: Check whether you run parse-git-config (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a prototype pollution flaw (CWE-1321) in the expandKeys function of parse-git-config v3.0.0. An attacker supplies specially crafted configuration data with properties like '__proto__' or constructor-related keys that, when processed by expandKeys, pollute the global prototype chain. No authentication or user interaction is required—the vulnerability is triggered by passing a malicious config object to the expandKeys function. An attacker can inject arbitrary properties into Object.prototype, which propagates to all objects in the application. Depending on how downstream code uses polluted properties, this could escalate to remote code execution, information disclosure, or other injection attacks. Affected versions: 0 through 3.0.0.

Affected products

jonschlinkert parse-git-config 0 through 3.0.0

Identifiers

CVE-2025-25975
GHSA-8g77-54rh-46hx

Timeline

2025-01-26: disclosed: Vulnerability reported as GitHub issue #14
2025-03-12: advisory: GHSA-8g77-54rh-46hx and CVE-2025-25975 published

References

https://github.com/jonschlinkert/parse-git-config/issues/14

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.