Which versions of csv-parse are affected by CVE-2026-85063?

csv-parse (npm) versions < 7.0.2 is affected.

Is there a fix for CVE-2026-85063?

Yes. CVE-2026-85063 is fixed in 7.0.2. Upgrade to this version or later.

Is CVE-2026-85063 exploitable, and should I be worried?

Whether CVE-2026-85063 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-85063 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-85063?

Upgrade csv-parse to 7.0.2 or later.

CVE-2026-85063 in csv-parse

Q: What is CVE-2026-85063?

CVE-2026-85063 is a medium-severity security vulnerability in csv-parse (npm), affecting versions < 7.0.2. It is fixed in 7.0.2.

Q: Is there a fix for CVE-2026-85063?

Yes. CVE-2026-85063 is fixed in 7.0.2. Upgrade to this version or later.

Q: Is CVE-2026-85063 exploitable, and should I be worried?

Whether CVE-2026-85063 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-85063 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-85063?

Upgrade csv-parse to 7.0.2 or later.

CVE-2026-85063

CVE-2026-85063 is a medium-severity security vulnerability in csv-parse (npm), affecting versions < 7.0.2. It is fixed in 7.0.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

node-csv: Prototype replacement still reachable via columns path

Workarounds

Disable usage of both the columns and group_columns_by_name options.

References

issue #496, PR #497

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).

Affected versions

csv-parse (< 7.0.2)

Security releases

csv-parse → 7.0.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem been patched.

Frequently Asked Questions

What is CVE-2026-85063? CVE-2026-85063 is a medium-severity security vulnerability in csv-parse (npm), affecting versions < 7.0.2. It is fixed in 7.0.2.
Which versions of csv-parse are affected by CVE-2026-85063? csv-parse (npm) versions < 7.0.2 is affected.
Is there a fix for CVE-2026-85063? Yes. CVE-2026-85063 is fixed in 7.0.2. Upgrade to this version or later.
Is CVE-2026-85063 exploitable, and should I be worried? Whether CVE-2026-85063 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-85063 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-85063? Upgrade csv-parse to 7.0.2 or later.