CVE-2026-53580

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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 weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

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

Trilium is an open-source hierarchical note-taking application. In versions prior to 0.104.0, the automatic image-download feature accepts file:// URLs in a note's img tags and reads the referenced local file with no path validation, allowing any authenticated user to disclose arbitrary files readable by the Trilium process. When a text note is saved, Trilium scans its HTML for image sources and downloads each external one; because the HTML sanitizer keeps file as an allowed scheme, a source such as file:///etc/passwd is passed straight to a filesystem read and its contents are stored as a note attachment the user can then retrieve. Pointing the same primitive at an unbounded source such as /dev/zero causes uncontrolled memory allocation that crashes the server process. The feature is enabled by default and is reachable through the web UI, the ETAPI, the web clipper, and note imports, requiring only an authenticated session or an ETAPI token. This issue is fixed in version 0.104.0

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit c417c901dfe4 (TriliumNext/Trilium)

Fix landed in TriliumNext/Trilium commit c417c901dfe4 — awaiting tagged release

https://github.com/TriliumNext/Trilium/commit/c417c901dfe45222c321fab1685f26730cc2068f
github Patch Available🟡 PoC Available

Arbitrary file disclosure and OOM crash via file:// in note content · Advisory · TriliumNext/Trilium · GitHub

https://github.com/TriliumNext/Trilium/security/advisories/GHSA-3gxr-j6g6-q75c

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-08-30 02:52 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 04:08 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-28 16:40 UTCEG score recompute
  6. 2026-08-28 15:42 UTCEG score recompute
  7. 2026-08-27 20:26 UTCEG score recompute
  8. 2026-08-27 20:14 UTCEG score recompute
  9. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53580?
CVE-2026-53580 is a high vulnerability published on August 27, 2026. Trilium is an open-source hierarchical note-taking application. In versions prior to 0.104.0, the automatic image-download feature accepts file:// URLs in a note's img tags and reads the referenced local file with no path validation, allowing any authenticated user to disclose arbitrary files…
When was CVE-2026-53580 disclosed?
CVE-2026-53580 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53580 actively exploited?
CVE-2026-53580 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 80.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53580?
CVE-2026-53580 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-53580?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53580, 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-53580

Explore →

Is Your Infrastructure Affected by CVE-2026-53580?

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

Start Free Scan →Browse All CVEs