CVE-2026-3187

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-02-25) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-8659 (ENISA EUVD) · GHSA-8p92-v8gg-gvcv (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability was identified in feiyuchuixue sz-boot-parent up to 1.3.2-beta. Affected by this issue is some unknown functionality of the file /api/admin/sys-file/upload of the component API Endpoint. Such manipulation leads to unrestricted upload. The attack may be launched remotely. The exploit is publicly available and might be used. Upgrading to version 1.3.3-beta can resolve this issue. The name of the patch is aefaabfd7527188bfba3c8c9eee17c316d094802. Upgrading the affected component is recommended. The project was informed beforehand and acted very professional: "We have introduced a whitelist restriction on the /api/admin/sys-file/upload endpoint via the oss.allowedExts and oss.allowedMimeTypes configuration options, allowing the specification of permitted file extensions and MIME types for uploads."

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
29th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Oct 31, 2026
Patch available. Sources: github_commit, github_release.
Web page

CVE/sz-boot-parent-Arbitrary_File_Upload.md at main · yuccun/CVE · GitHub

https://github.com/yuccun/CVE/blob/main/sz-boot-parent-Arbitrary_File_Upload.md
GitHub release Patch Available

v1.3.3-beta

Patch available: feiyuchuixue/sz-boot-parent v1.3.3-beta

https://github.com/feiyuchuixue/sz-boot-parent/releases/tag/v1.3.3-beta
GitHub commit Patch Available

commit aefaabfd7527 (feiyuchuixue/sz-boot-parent)

Patch available: feiyuchuixue/sz-boot-parent v1.3.3-beta (contains commit aefaabfd7527)

https://github.com/feiyuchuixue/sz-boot-parent/commit/aefaabfd7527188bfba3c8c9eee17c316d094802
Web page

GitHub - feiyuchuixue/sz-boot-parent: Backend scaffold for Sz-Admin, built with Spring Boot 4, featuring RBAC, dynamic menus, code generation, data scope permissions, Excel import/export, OSS integration, and WebSocket support. · GitHub

https://github.com/feiyuchuixue/sz-boot-parent/

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 77× 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 99 of 274 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 175 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-3187?
CVE-2026-3187 is a critical-severity vulnerability; its CVE record was published on February 25, 2026. A vulnerability was identified in feiyuchuixue sz-boot-parent up to 1.3.2-beta. Affected by this issue is some unknown functionality of the file /api/admin/sys-file/upload of the component API Endpoint. Such manipulation leads to unrestricted upload. The attack may be launched remotely. The exploit…
When was the CVE record for CVE-2026-3187 published?
The CVE record for CVE-2026-3187 was published on February 25, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-3187 actively exploited?
CVE-2026-3187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3187?
CVE-2026-3187 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-3187?
A fix for CVE-2026-3187 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3187

Explore →

Is Your Infrastructure Affected by CVE-2026-3187?

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

Book a Demo →Browse All CVEs