CVE-2026-12143

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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: epss, secondary
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 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)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 20, 2026

Advisory Details (6)

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

HTML Standard

https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#multipart-form-data
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

Vendor Advisories for CVE-2026-12143(20)

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatansible-automation-platform/automation-portal:17870471142026-08-18redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17865867892026-08-18redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17852301472026-08-04redhat
redhatmta/mta-ui-rhel9:17851690132026-08-04redhat
redhatdevspaces/dashboard-rhel9:17847371502026-07-29redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-132026-07-29redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847246992026-07-28redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17847137412026-07-28redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatform-data2026-07-20redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatrhdh/rhdh-hub-rhel9:17842109212026-07-20redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat
redhatdotnet8-0-main-8.0.128-1.1.hum12026-07-10redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17833571402026-07-08redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17833571162026-07-07redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:17828394942026-07-01redhat
redhatopenshift-service-mesh/kiali-rhel9:17822014662026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018122026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel8:17822875802026-06-29redhat
redhatopenshift-service-mesh/kiali-rhel9:17822018332026-06-29redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-form-data3.0.0-2 ... 4.0.6+~2.1.0-1 (11 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-form-data4.0.0-1 ... 4.0.6+~2.1.0-1 (7 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-form-data4.0.1-2, 4.0.4+~2.1.0-1, 4.0.5+~2.1.0-1, 4.0.6+~2.1.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-form-data4.0.1-2, 4.0.4+~2.1.0-1, 4.0.5+~2.1.0-14.0.6+~2.1.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
form-data—4.0.6—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 39× in last 7d / 152× 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 228 total refreshes for this CVE.

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

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 August 20, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 57.0% of all scored CVEs.
What is the CVSS score of CVE-2026-12143?
CVE-2026-12143 has a CVSS v3 base score of 7.5 (NVD).
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.

Start Free Scan →Browse All CVEs