CVE-2026-48796

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-62186 (ENISA EUVD) · GHSA-85jm-cwp2-mvpv (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

CefSharp provides .NET bindings for the Chromium Embedded Framework for Windows Forms and Windows Presentation Foundation applications. Prior to version 148.0.90, CefSharp/SchemeHandler/FolderSchemeHandlerFactory.cs used filePath.StartsWith(rootFolder, StringComparison.OrdinalIgnoreCase) to decide whether a decoded and canonicalized request path remained inside rootFolder. That raw prefix test did not enforce a directory boundary, so a request such as ..%2fwww2/secret.txt could escape a configured www directory into a sibling www2 directory whose path shared the same string prefix. Applications that register FolderSchemeHandlerFactory for a custom scheme or an HTTP or HTTPS scheme can therefore serve local files outside the intended root when an attacker can cause the embedded browser to request the crafted URL. The issue affects both Unix-style paths such as /tmp/app/www2 and Windows paths such as C:\app\www2, and the fix appends a directory separator to the normalized root before comparison while rejecting null bytes and alternate data stream syntax. This issue is fixed in version 148.0.90.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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
33rd
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 every mission impact level.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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (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.

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

June 30, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

`FolderSchemeHandlerFactory` path boundary check can expose files outside the configured root folder · Advisory · cefsharp/CefSharp · GitHub

https://github.com/cefsharp/CefSharp/security/advisories/GHSA-85jm-cwp2-mvpv
GitHub release Patch Available

v148.0.90

Patch available: cefsharp/CefSharp v148.0.90

https://github.com/cefsharp/CefSharp/releases/tag/v148.0.90
GitHub commit Patch Available

commit 3475c7ef1411 (cefsharp/CefSharp)

Patch available: cefsharp/CefSharp v148.0.90 (contains commit 3475c7ef1411)

https://github.com/cefsharp/CefSharp/commit/3475c7ef14119f67ec3720866bb3e4b1c6c68632

Vendor Advisories for CVE-2026-48796(1)

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

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
CefSharp.Common100.0.120-pre ... 99.2.90 (218 versions)
  • every version up to 148.0.90: fixed in 148.0.90
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 35× 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.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-25 14:23 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-22 23:04 UTCEG score recompute
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-18 03:34 UTCEG score recompute
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-13 18:24 UTCOSV refresh
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-12 16:00 UTCEG score recompute
  22. 2026-10-11 19:43 UTCEG score recompute
  23. 2026-10-11 16:58 UTCEG score recompute
  24. 2026-10-11 14:22 UTCEG score recompute
  25. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 57 more
  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-09-23 07:19 UTCEG score recompute
  16. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-09-18 06:48 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-09-14 00:47 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-12 15:09 UTCEG score recompute
  24. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  26. 2026-09-09 22:59 UTCEG score recompute
  27. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-09-06 14:35 UTCEG score recompute
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-08-30 18:02 UTCEG score recompute
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  39. 2026-08-27 22:41 UTCEG score recompute
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-08-24 21:08 UTCEG score recompute
  44. 2026-08-23 20:28 UTCEG score recompute
  45. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-08-22 20:29 UTCEG score recompute
  47. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-08-21 19:28 UTCEG score recompute
  49. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-19 19:21 UTCEG score recompute
  51. 2026-08-19 18:23 UTCEG score recompute
  52. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-08-18 22:24 UTCEG score recompute
  54. 2026-07-30 22:20 UTCEG score recompute
  55. 2026-07-26 13:51 UTCEG score recompute
  56. 2026-07-23 03:18 UTCEG score recompute
  57. 2026-06-30 19:31 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-48796?
CVE-2026-48796 is a medium-severity vulnerability; its CVE record was published on June 30, 2026. CefSharp provides .NET bindings for the Chromium Embedded Framework for Windows Forms and Windows Presentation Foundation applications. Prior to version 148.0.90, CefSharp/SchemeHandler/FolderSchemeHandlerFactory.cs used filePath.StartsWith(rootFolder, StringComparison.OrdinalIgnoreCase) to decide…
When was the CVE record for CVE-2026-48796 published?
The CVE record for CVE-2026-48796 was published on June 30, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-48796 actively exploited?
CVE-2026-48796 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48796?
CVE-2026-48796 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48796?
A fix for CVE-2026-48796 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48796 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-48796

Explore →

Is Your Infrastructure Affected by CVE-2026-48796?

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

Book a Demo →Browse All CVEs