CVE-2026-12143

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:harborist, epss
Trending — Patch released this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

form-data is a library for creating readable multipart/form-data streams. In versions through 4.0.5, the field argument to FormData#append and the filename option are concatenated verbatim into the Content-Disposition header without escaping carriage return (CR), line feed (LF), or double-quote (") characters. An application that passes attacker-controlled data as a field name or filename (for example, an API gateway that turns JSON object keys into multipart field names) allows the attacker to terminate the header line and inject additional headers, or to smuggle entire additional multipart parts, into the request the application forwards to a backend. This can let the attacker add or override form fields (e.g. set is_admin=true) seen by the downstream parser. This is an instance of CWE-93 (CRLF injection). The fix escapes CR, LF, and " as %0D, %0A, and %22 in field names and filenames, matching the serialization browsers use per the WHATWG HTML multipart/form-data encoding algorithm. Exploitation requires the consuming application to use untrusted input as a field name or filename; applications that use only fixed/trusted field names are not affected. Fixed in 2.5.6, 3.0.5, and 4.0.6.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
32.8%
KEV
Not listed

Published

June 12, 2026

Last Modified

July 6, 2026

Advisory Details (6)

Auto-updated Jun 12, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

CRLF injection in form-data via unescaped multipart field names and filenames · Advisory · form-data/form-data · GitHub

https://github.com/form-data/form-data/security/advisories/GHSA-hmw2-7cc7-3qxx
github_commit

commit c7133499c2ee (form-data/form-data)

Fix landed in form-data/form-data commit c7133499c2ee — awaiting tagged release

https://github.com/form-data/form-data/commit/c7133499c2ee1b80c678e411244f4442bf902045
github_commit

commit be3f3cf55397 (form-data/form-data)

Fix landed in form-data/form-data commit be3f3cf55397 — awaiting tagged release

https://github.com/form-data/form-data/commit/be3f3cf553978bac15a5182f1f3c3d2d38ccf229
github_commit

commit 64190db548c0 (form-data/form-data)

Fix landed in form-data/form-data commit 64190db548c0 — awaiting tagged release

https://github.com/form-data/form-data/commit/64190db548c0179e37206858e39f27cf513e9435
generic

CWE - CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection') (4.20)

https://cwe.mitre.org/data/definitions/93.html

Patch Availability(6)

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
form-data4.0.6

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 92× 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.

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

Frequently asked(5)

What is CVE-2026-12143?
CVE-2026-12143 is a high vulnerability published on June 12, 2026. form-data is a library for creating readable multipart/form-data streams. In versions through 4.0.5, the field argument to FormData#append and the filename option are concatenated verbatim into the Content-Disposition header without escaping carriage return (CR), line feed (LF), or double-quote (")…
When was CVE-2026-12143 disclosed?
CVE-2026-12143 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12143 actively exploited?
CVE-2026-12143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12143?
CVE-2026-12143 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-12143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12143, 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-12143

Explore →

Is Your Infrastructure Affected by CVE-2026-12143?

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