CVE-2026-48026

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th 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
8.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

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

The CVE record's description, written by its CNA (GitHub, Inc.), states the affected versions: "Prior to version 1.81.1 of the open source edition and 1.84.0 of the enterprise edition, lakeFS Web UI renders markdown files from repository objects without sanitizing the resulting HTML." No release containing a fix is confirmed on record.

lakeFS is an open-source tool that transforms object storage into a Git-like repositories. Prior to version 1.81.1 of the open source edition and 1.84.0 of the enterprise edition, lakeFS Web UI renders markdown files from repository objects without sanitizing the resulting HTML. A user with write access to any repository branch can commit a .md object containing arbitrary HTML/JavaScript. Any other user who opens that object, or who navigates to a repository or directory containing a malicious README.md, executes the attacker-supplied script in their own authenticated session. lakeFS fixes the issue in v1.81.1 and lakeFS Enterprise fixes the issue in in v1.84.0. Enterprise customers using older versions can temporarily disable Markdown rendering by adding YAML to their config. No workaround exists for OSS release. Users are advised to upgrade to the latest version for both lakeFS and lakeFS-Enterprise.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/100

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 (value × EchelonGraph’s weight)
Severity87% × 45%
The EG Score, 8.7 of 10.
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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 7, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
No fix on record yet. Sources: github.
Web page

lakeFS/webui/src/pages/repositories/repository/fileRenderers/useMarkdownProcessor.tsx at 77539527e987fb05c27e3e74c59c0a46a05c47a0 · treeverse/lakeFS · GitHub

https://github.com/treeverse/lakeFS/blob/77539527e987fb05c27e3e74c59c0a46a05c47a0/webui/src/pages/repositories/repository/fileRenderers/useMarkdownProcessor.tsx
GitHub advisoryMentions a patch (unverified)

stored XSS in rendered markdown previews via raw HTML · Advisory · treeverse/lakeFS · GitHub

Affected: v1.81.1.

https://github.com/treeverse/lakeFS/security/advisories/GHSA-c2r5-5j4w-2xff

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 44× 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 114 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 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48026?
CVE-2026-48026 is a high-severity vulnerability; its CVE record was published on August 7, 2026. lakeFS is an open-source tool that transforms object storage into a Git-like repositories. Prior to version 1.81.1 of the open source edition and 1.84.0 of the enterprise edition, lakeFS Web UI renders markdown files from repository objects without sanitizing the resulting HTML. A user with write…
When was the CVE record for CVE-2026-48026 published?
The CVE record for CVE-2026-48026 was published on August 7, 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-48026 actively exploited?
CVE-2026-48026 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48026?
CVE-2026-48026 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48026?
No fix for CVE-2026-48026 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (GitHub, Inc.), states the affected versions: "Prior to version 1.81.1 of the open source edition and 1.84.0 of the enterprise edition, lakeFS Web UI renders markdown files from repository objects without sanitizing the resulting HTML." No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48026?

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

Book a Demo →Browse All CVEs