CVE-2026-12143

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-15. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-36524 (ENISA EUVD) · GHSA-hmw2-7cc7-3qxx (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 12, 2026

Last Modified

September 11, 2026

Advisory Details (6)

Auto-updated Jun 12, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

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
Web page

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

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

Patch Availability(32)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mod-arch-eval-hub-rhel9:17918612142026-10-19redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609692026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896155932026-09-17redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17896609832026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896150952026-09-17redhat
redhatform-data2026-09-10redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17883186612026-09-09redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17883222432026-09-03redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17882609412026-09-03redhat
redhatdevspaces/code-rhel9:17877627932026-09-01redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17877363962026-09-01redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17875903902026-09-01redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17872506172026-08-27redhat
redhatrhacm2/console-rhel9:17873392132026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873417802026-08-26redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870793642026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870650522026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872642502026-08-25redhat
redhatopenshift4/ose-console-rhel9:17870141972026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-08-25redhat
redhatopenshift4/ose-console-rhel9:17870808922026-08-25redhat
redhatautomation-platform-ui-0:2.6.13-1.el9ap2026-08-24redhat
npmform-data @ 2.5.6 (fixes < 2.5.6)—ghsa
npmform-data @ 3.0.5 (fixes >= 3.0.0, < 3.0.5)—ghsa
npmform-data @ 4.0.6 (fixes >= 4.0.0, < 4.0.6)—ghsa

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 rangeFix by version rangeDependents
node-form-data3.0.0-2 ... 4.0.6+~2.1.0-1 (11 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-form-data4.0.0-1 ... 4.0.6+~2.1.0-1 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
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
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-form-data4.0.1-2, 4.0.4+~2.1.0-1, 4.0.5+~2.1.0-1
  • every version up to 4.0.6+~2.1.0-1: fixed in 4.0.6+~2.1.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
form-data—
  • every version up to 2.5.6: fixed in 2.5.6
  • 3.0.0 up to 3.0.5: fixed in 3.0.5
  • 4.0.0 up to 4.0.6: fixed in 4.0.6
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 386 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 286 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-11-12 14:56 UTCEchelonGraph re-scored
  4. 2026-11-12 14:56 UTCVendor advisory
  5. 2026-11-12 14:56 UTCGHSA enrichmentGHSA-hmw2-7cc7-3qxx · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-11-06 03:57 UTCEchelonGraph re-scored
  13. 2026-11-06 03:57 UTCVendor advisory
  14. 2026-11-06 03:57 UTCGHSA enrichmentGHSA-hmw2-7cc7-3qxx · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-hmw2-7cc7-3qxx · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-01 07:59 UTCEchelonGraph re-scored
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-30 16:57 UTCEchelonGraph re-scored
  24. 2026-10-30 16:57 UTCVendor advisory
  25. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
Show 75 more
  1. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-25 14:49 UTCEchelonGraph re-scored
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-24 05:59 UTCEchelonGraph re-scored
  9. 2026-10-24 05:59 UTCVendor advisory
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-18 05:04 UTCEchelonGraph re-scored
  17. 2026-10-17 18:54 UTCEchelonGraph re-scored
  18. 2026-10-17 18:54 UTCVendor advisory
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-10-12 16:36 UTCEchelonGraph re-scored
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  26. 2026-10-11 20:12 UTCEchelonGraph re-scored
  27. 2026-10-11 18:24 UTCEchelonGraph re-scored
  28. 2026-10-11 14:58 UTCEchelonGraph re-scored
  29. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  30. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-10-03 08:39 UTCOSV refresh
  39. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  40. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  42. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  43. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  44. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  45. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  46. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  47. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-09-14 03:58 UTCEchelonGraph re-scored
  49. 2026-09-14 03:58 UTCVendor advisory
  50. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  51. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  53. 2026-09-11 13:24 UTCEchelonGraph re-scored
  54. 2026-09-11 13:24 UTCVendor advisory
  55. 2026-09-11 12:20 UTCEchelonGraph re-scored
  56. 2026-09-11 12:20 UTCVendor advisory
  57. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  58. 2026-09-10 13:22 UTCEchelonGraph re-scored
  59. 2026-09-10 13:22 UTCVendor advisory
  60. 2026-09-10 12:25 UTCEchelonGraph re-scored
  61. 2026-09-10 12:25 UTCVendor advisory
  62. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  63. 2026-09-09 13:40 UTCEchelonGraph re-scored
  64. 2026-09-09 13:40 UTCVendor advisory
  65. 2026-09-09 12:38 UTCEchelonGraph re-scored
  66. 2026-09-09 12:38 UTCVendor advisory
  67. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  68. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  69. 2026-09-07 13:24 UTCEchelonGraph re-scored
  70. 2026-09-07 13:24 UTCVendor advisory
  71. 2026-09-07 12:32 UTCEchelonGraph re-scored
  72. 2026-09-07 12:32 UTCVendor advisory
  73. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  74. 2026-09-04 13:29 UTCEchelonGraph re-scored
  75. 2026-09-04 13:29 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-12143?
CVE-2026-12143 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-12143 published?
The CVE record for CVE-2026-12143 was published on June 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-12143 actively exploited?
CVE-2026-12143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12143?
CVE-2026-12143 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12143?
A fix for CVE-2026-12143 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12143 are linked in the Vendor Advisories panel on this page.

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.