CVE-2026-57581

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 62% 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 — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DotVVM is an open source MVVM framework for web applications. Prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, applications with configured file upload storage allow unauthenticated users to submit files directly to DotvvmFileUploadMiddleware without an X-DotVVM-UploadToken generated by the FileUpload component. An attacker can repeatedly upload files and fill application storage, causing denial of service. DotvvmConfiguration.Security.AuthorizeFileUpload can additionally restrict which users may upload files. This issue is fixed in versions 4.2.11, 4.3.15, and 5.0.0-preview09-final.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 16, 2026

Advisory Details (5)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

DotVVM 4.3.15 security patch

Patch available: riganti/dotvvm v4.3.15

https://github.com/riganti/dotvvm/releases/tag/v4.3.15
github_commit Patch Available

commit 6af982bbe3b0 (riganti/dotvvm)

Patch available: riganti/dotvvm v5.0.0-preview11 (contains commit 6af982bbe3b0)

https://github.com/riganti/dotvvm/commit/6af982bbe3b00bdac00f1c0efe9365d52db642ef
github_commit

commit 4fc26a8591c7 (riganti/dotvvm)

Fix landed in riganti/dotvvm commit 4fc26a8591c7 — awaiting tagged release

https://github.com/riganti/dotvvm/commit/4fc26a8591c76fb92ed701352c2a84120cf926c5
github_commit Patch Available

commit 1635245b5eaf (riganti/dotvvm)

Patch available: riganti/dotvvm v4.3.15 (contains commit 1635245b5eaf)

https://github.com/riganti/dotvvm/commit/1635245b5eaf9ccf8e3536b9d8b1941819526585
github Patch Available

Unrestricted file upload · Advisory · riganti/dotvvm · GitHub

https://github.com/riganti/dotvvm/security/advisories/GHSA-2rm3-333w-xvc4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-09-21 08:04 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-20 09:51 UTCEG score recompute
  4. 2026-09-19 11:39 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 13:20 UTCEG score recompute
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-16 16:55 UTCEG score recompute
  9. 2026-09-16 16:00 UTCEG score recompute
  10. 2026-09-16 14:57 UTCEG score recompute
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-14 18:31 UTCEG score recompute
  14. 2026-09-14 17:45 UTCEG score recompute
  15. 2026-09-14 17:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57581?
CVE-2026-57581 is a medium vulnerability published on September 14, 2026. DotVVM is an open source MVVM framework for web applications. Prior to 4.2.11, 4.3.15, and 5.0.0-preview09-final, applications with configured file upload storage allow unauthenticated users to submit files directly to DotvvmFileUploadMiddleware without an X-DotVVM-UploadToken generated by the…
When was CVE-2026-57581 disclosed?
CVE-2026-57581 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57581 actively exploited?
CVE-2026-57581 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.3% of all scored CVEs.
What is the CVSS score of CVE-2026-57581?
CVE-2026-57581 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-57581?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57581, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57581?

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