Prototype Pollution Vulnerability in parse-git-config

published 2025-03-12 19 mo ago modified 2026-06-17 4 mo ago also GHSA-8g77-54rh-46hx , EUVD-2025-6799

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits: 0; none known

An issue in parse-git-config v.3.0.0 allows an attacker to obtain sensitive information via the expandKeys function

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-25975 updated 2026-06-28 cvss 7.5

parse-git-config: Prototype Pollution Vulneralbility in parse-git-config

Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 19 mo ago (2025-03-19)

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/jonschlinkert/parse-git-config/issues/14 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	parse-git-config	<=3.0.0	no fix listed

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

github.com /jonschlinkert/parse-git-config/issues/14
exploit, web, issue-tracking
nvd.nist.gov /vuln/detail/CVE-2025-25975
advisory
github.com /jonschlinkert/parse-git-config
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary