CVE-2026-19481

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-10-02. 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
Trending — 4 sources updated this week

Also known asEUVD-2026-57757 (ENISA EUVD) · GHSA-x8mw-p69m-v3mx (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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

@fastify/busboy is a multipart form-data parser. In versions 1.0.0 through 3.2.0, an attacker who can submit multipart form-data can crash the parser by sending a part header whose name is a prototype-inherited property such as __proto__ or constructor. The internal header parser stores headers in a plain JavaScript object and assumes each value is an array, so an inherited property name resolves to a truthy non-array value and triggers a TypeError. In the common pipe integration the failure surfaces as an error event, but in direct write or end usage the exception is thrown synchronously and can terminate the Node.js process, causing an unauthenticated denial of service. The issue is fixed in @fastify/busboy 3.2.1, which creates the header object with a null prototype. Users should upgrade to 3.2.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.5%
EPSS %ILE
42nd
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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 none (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

August 13, 2026

Last Modified

September 3, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available. Sources: github.
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
GitHub advisoryMentions a patch (unverified)

@fastify/busboy vulnerable to Denial of Service via prototype-named multipart part header · Advisory · fastify/busboy · GitHub

Affected: version 3.2.1.

https://github.com/fastify/busboy/security/advisories/GHSA-x8mw-p69m-v3mx

Vendor Advisories for CVE-2026-19481(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mod-arch-model-registry-rhel9:17918534322026-10-21redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17918609182026-10-19redhat
npm@fastify/busboy @ 3.2.1 (fixes >= 1.0.0, < 3.2.1)—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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@fastify/busboy—
  • 1.0.0 up to 3.2.1: fixed in 3.2.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 49× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 138 refreshes 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 38 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

npm:@fastify/busboy

Frequently asked(5)

What is CVE-2026-19481?
CVE-2026-19481 is a high-severity vulnerability; its CVE record was published on August 13, 2026. @fastify/busboy is a multipart form-data parser. In versions 1.0.0 through 3.2.0, an attacker who can submit multipart form-data can crash the parser by sending a part header whose name is a prototype-inherited property such as proto or constructor. The internal header parser stores headers in a…
When was the CVE record for CVE-2026-19481 published?
The CVE record for CVE-2026-19481 was published on August 13, 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 3, 2026; the record at its source may have been updated since.
Is CVE-2026-19481 actively exploited?
CVE-2026-19481 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19481?
CVE-2026-19481 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-19481?
A fix for CVE-2026-19481 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-19481 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-19481

Explore →

Is Your Infrastructure Affected by CVE-2026-19481?

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

Book a Demo →Browse All CVEs