CVE-2026-48818

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.4%, top 70% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Starlette is a lightweight ASGI framework/toolkit. In versions 1.0.1 and earlier, StaticFiles on Windows is vulnerable to SSRF. An UNC path such as \\attacker.com\share can cause os.path.realpath to initiate an outbound SMB connection before the path is rejected, exposing the service account’s NTLMv2 credentials for offline cracking or relay even though the HTTP response is only a 404. The issue affects default follow_symlink=False deployments, including frameworks built on Starlette such as FastAPI; POSIX systems and follow_symlink=True are unaffected. The issue is fixed in 1.1.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

June 15, 2026

Last Modified

August 4, 2026

Advisory Details (4)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

SSRF and NTLM credential theft via UNC paths in StaticFiles on Windows · Advisory · Kludex/starlette · GitHub

https://github.com/Kludex/starlette/security/advisories/GHSA-wqp7-x3pw-xc5r
github_release Patch Available

Version 1.1.0

Patch available: Kludex/starlette 1.1.0

https://github.com/Kludex/starlette/releases/tag/1.1.0
github_pr Patch Available

Reject absolute paths in `StaticFiles.lookup_path`

Patch available: Kludex/starlette 1.1.0 (PR #3287 merged 2026-05-23)

https://github.com/Kludex/starlette/pull/3287
github_commit Patch Available

commit fd53168a7767 (Kludex/starlette)

Patch available: Kludex/starlette 1.1.0 (contains commit fd53168a7767)

https://github.com/Kludex/starlette/commit/fd53168a7767b6b55ba5af787fd88f49e33cabc5

Vendor Advisories for CVE-2026-48818(4)

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 / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-spyre-rhel9:17823529192026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat

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)
PyPI(1)
PackageVulnerable rangeFixed inDependents
starlette0.1.0 ... 1.0.1 (192 versions)1.1.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 99× 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 172 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48818?
CVE-2026-48818 is a high vulnerability published on June 15, 2026. Starlette is a lightweight ASGI framework/toolkit. In versions 1.0.1 and earlier, StaticFiles on Windows is vulnerable to SSRF. An UNC path such as \\attacker.com\share can cause os.path.realpath to initiate an outbound SMB connection before the path is rejected, exposing the service account’s…
When was CVE-2026-48818 disclosed?
CVE-2026-48818 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48818 actively exploited?
CVE-2026-48818 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 69.9% of all scored CVEs.
What is the CVSS score of CVE-2026-48818?
CVE-2026-48818 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48818, 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-48818

Explore →

Is Your Infrastructure Affected by CVE-2026-48818?

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

Start Free Scan →Browse All CVEs