CVE-2026-9673

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-05-28. the CNA's CVSS baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:snyk, epss, ghsa
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

A fix is available — apply it.

Versions of the package json-2-csv from 3.15.0 and before 5.5.11 are vulnerable to CSV Injection via the preventCsvInjection option which can be bypassed. An attacker can inject formulas into CSV files, which execute when the files are opened in spreadsheet applications.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 7, 2026

Advisory Details (3)

Auto-updated May 29, 2026
⚠️ Active exploitation confirmed. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🔴 Active Exploitation

CSV Injection in json-2-csv | CVE-2026-9673 | Snyk

https://security.snyk.io/vuln/SNYK-JS-JSON2CSV-14221326
github_commit

commit 0fdd0bb6d027 (mrodrig/json-2-csv)

Fix landed in mrodrig/json-2-csv commit 0fdd0bb6d027 — awaiting tagged release

https://github.com/mrodrig/json-2-csv/commit/0fdd0bb6d0273178cd940afc323ccbce19688229
generic🟡 PoC Available

json-2-csv-injection-bypass.md · GitHub

https://gist.github.com/whoamins/299745a2d36b482b44e9613b78e40613

Vendor Advisories for CVE-2026-9673(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
json-2-csv—5.5.11—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 169 total refreshes for this CVE.

  1. 2026-09-01 04:40 UTCEPSS rescore
  2. 2026-08-30 19:18 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:47 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 05:07 UTCEG score recompute
  9. 2026-08-25 05:07 UTCVendor advisory
  10. 2026-08-24 14:18 UTCEPSS rescore
  11. 2026-08-23 14:51 UTCEG score recompute
  12. 2026-08-23 14:51 UTCVendor advisory
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 20:27 UTCEG score recompute
  16. 2026-08-21 20:27 UTCVendor advisory
  17. 2026-08-20 22:56 UTCEPSS rescore
  18. 2026-08-20 11:11 UTCEG score recompute
  19. 2026-08-20 11:11 UTCVendor advisory
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 09:06 UTCEG score recompute
  24. 2026-08-17 09:06 UTCVendor advisory
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 02:42 UTCEG score recompute
  2. 2026-08-16 02:42 UTCVendor advisory
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 01:36 UTCEG score recompute
  5. 2026-08-15 01:36 UTCVendor advisory
  6. 2026-08-15 01:31 UTCEPSS rescore
  7. 2026-08-14 01:22 UTCVendor advisory
  8. 2026-08-13 00:41 UTCEG score recompute
  9. 2026-08-13 00:41 UTCVendor advisory
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 00:27 UTCEG score recompute
  12. 2026-08-12 00:27 UTCVendor advisory
  13. 2026-08-11 13:43 UTCEPSS rescore
  14. 2026-08-11 00:08 UTCEG score recompute
  15. 2026-08-11 00:08 UTCVendor advisory
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 19:00 UTCEG score recompute
  18. 2026-08-09 19:00 UTCVendor advisory
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-08 18:46 UTCEG score recompute
  21. 2026-08-08 18:46 UTCVendor advisory
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 16:30 UTCEPSS rescore
  24. 2026-08-07 15:43 UTCVendor advisory
  25. 2026-08-06 16:42 UTCEG score recompute
  26. 2026-08-06 16:42 UTCVendor advisory
  27. 2026-08-06 13:47 UTCEPSS rescore
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-05 16:13 UTCEG score recompute
  30. 2026-08-05 16:13 UTCVendor advisory
  31. 2026-08-04 15:10 UTCEPSS rescore
  32. 2026-08-04 10:39 UTCEPSS rescore
  33. 2026-08-03 16:17 UTCEG score recompute
  34. 2026-08-03 16:17 UTCVendor advisory
  35. 2026-08-03 10:36 UTCEPSS rescore
  36. 2026-08-02 15:09 UTCEG score recompute
  37. 2026-08-02 15:09 UTCVendor advisory
  38. 2026-08-02 02:27 UTCEPSS rescore
  39. 2026-08-01 14:55 UTCEG score recompute
  40. 2026-08-01 14:55 UTCVendor advisory
  41. 2026-08-01 04:16 UTCEPSS rescore
  42. 2026-07-31 07:03 UTCEG score recompute
  43. 2026-07-31 07:03 UTCVendor advisory
  44. 2026-07-30 16:28 UTCEPSS rescore
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-29 15:34 UTCVendor advisory
  47. 2026-07-29 14:37 UTCEG score recompute
  48. 2026-07-29 14:37 UTCVendor advisory
  49. 2026-07-28 15:37 UTCEPSS rescore
  50. 2026-07-27 14:14 UTCEPSS rescore
  51. 2026-07-27 09:53 UTCEG score recompute
  52. 2026-07-27 09:53 UTCVendor advisory
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-25 14:18 UTCEPSS rescore
  55. 2026-07-24 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:23 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-21 15:25 UTCEPSS rescore
  60. 2026-07-21 15:25 UTCEPSS rescore
  61. 2026-07-20 17:08 UTCEPSS rescore
  62. 2026-07-19 14:31 UTCEPSS rescore
  63. 2026-07-19 02:29 UTCEPSS rescore
  64. 2026-07-16 17:03 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-14 15:40 UTCMITRE cvelistV5CVSS v4 → 7
  68. 2026-07-13 22:31 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-12 05:46 UTCEPSS rescore
  71. 2026-07-11 21:42 UTCVendor advisory
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-09 19:10 UTCEPSS rescore
  74. 2026-07-08 22:48 UTCVendor advisory
  75. 2026-07-08 15:16 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-9673?
CVE-2026-9673 is a medium vulnerability published on May 28, 2026. Versions of the package json-2-csv from 3.15.0 and before 5.5.11 are vulnerable to CSV Injection via the preventCsvInjection option which can be bypassed. An attacker can inject formulas into CSV files, which execute when the files are opened in spreadsheet applications.
When was CVE-2026-9673 disclosed?
CVE-2026-9673 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9673 actively exploited?
CVE-2026-9673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-9673?
CVE-2026-9673 has a CVSS v4.0 base score of 6.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-9673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9673, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9673

Explore →

Is Your Infrastructure Affected by CVE-2026-9673?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs