How severe is GHSA-8cw4-87c7-c6xx?

No CVSS score has been assigned to GHSA-8cw4-87c7-c6xx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8cw4-87c7-c6xx?

GHSA-8cw4-87c7-c6xx affects the following packages: csv-parse (npm). Ecosystems affected: npm.

How do I fix GHSA-8cw4-87c7-c6xx?

Update csv-parse to 7.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8cw4-87c7-c6xx is resolved across your whole dependency graph.

How do I detect GHSA-8cw4-87c7-c6xx in my npm dependencies?

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

How do I mitigate GHSA-8cw4-87c7-c6xx 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.

Is GHSA-8cw4-87c7-c6xx actively exploited in the wild?

No public exploit code has been indexed for GHSA-8cw4-87c7-c6xx 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-8cw4-87c7-c6xx?

GHSA-8cw4-87c7-c6xx has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th 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-8cw4-87c7-c6xx?

GHSA-8cw4-87c7-c6xx 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-8cw4-87c7-c6xx published, and has it been updated?

GHSA-8cw4-87c7-c6xx was published on September 8, 2026 and was last updated on September 8, 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

node-csv: Prototype replacement still reachable via columns pathGHSA-8cw4-87c7-c6xx

Fix: adaltas/node-csv#497

GHSA-8cw4-87c7-c6xx is a CWE-1321 vulnerability in csv-parse. A fix is available for csv-parse — see the affected versions and patch details below.

Also known asCVE-2026-85063

Published

Sep 8, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8cw4-87c7-c6xx.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

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

csv-parsenpm

12.7Mdownloads / week

Description

node-csv is a full-featured CSV parser with a simple API that is tested against large datasets. Prior to 7.0.2, csv-parse with the columns and group_columns_by_name options enabled treats a duplicate proto header as an existing property in packages/csv-parse/lib/api/index.js, assigns an attacker-controlled array through obj['proto'], and replaces the parsed record object's prototype. A malicious CSV header can therefore inject inherited array values into the returned record, hide those inherited values from JSON serialization, and affect property enumeration and type or shape checks in applications that process the record. This issue is fixed in version 7.0.2.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`csv-parse`	all versions	7.0.2`npm install csv-parse@7.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for csv-parse, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update csv-parse to 7.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8cw4-87c7-c6xx 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

A moderate impact prototype pollution flaw was found in the node-csv csv-parse library, which is shipped in a number of Red Hat products. When csv-parse is configured with both the columns and group_columns_by_name options, a remote attacker able to control CSV input can craft a CSV header containing a duplicate…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for GHSA-8cw4-87c7-c6xx (CC BY 4.0)

Frequently Asked Questions

### Impact With columns: true and group_columns_by_name: true, a duplicated __proto__ header causes the duplicate-column branch to assign an array to obj['__proto__'], invoking the __proto__ setter and replacing the parsed record object's prototype with attacker-controlled data. Fixed in 7.0.2 (Object.hasOwn duplicate check + Object.defineProperty assignment). ### Patches The problem been patched. ### Workarounds Disable usage of both the columns and group_columns_by_name options. ### References issue #496, PR #497

O3 Security · Impact-Aware SCA

Is GHSA-8cw4-87c7-c6xx in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works