CVE-2026-48996

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-67163 (ENISA EUVD)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Trilium is an open-source hierarchical note-taking application. In versions up to and including 0.103.0, the default-on "Safe import" filter does not sanitize note titles, and the GeoMap note view interpolates a marker note's title into raw HTML that is rendered as innerHTML, allowing an attacker-supplied import archive to inject script that runs when the map is displayed. Because Safe import neutralizes scripts but never escapes titles, a note whose title contains an HTML event-handler payload survives the import and executes as soon as the victim opens the GeoMap that renders its marker. On the desktop client the Electron renderer runs with Node integration enabled, so the injected JavaScript escalates from cross-site scripting to full remote code execution on the victim's machine. This issue is fixed in version 0.104.0.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
16th
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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 27, 2026

Last Modified

October 14, 2026

Advisory Details (2)

Auto-updated Oct 3, 2026
Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Note Import to RCE via Legacy GeoMap Note · Advisory · TriliumNext/Trilium · GitHub

https://github.com/TriliumNext/Trilium/security/advisories/GHSA-7qfw-c9gj-2xq2
GitHub commit

commit 5245ad70f6ec (TriliumNext/Trilium)

Fix landed in TriliumNext/Trilium commit 5245ad70f6ec — awaiting tagged release

https://github.com/TriliumNext/Trilium/commit/5245ad70f6ecc54e0309fb83e596f15fe5dc5bf6

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 124 rows 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 24 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48996?
CVE-2026-48996 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. Trilium is an open-source hierarchical note-taking application. In versions up to and including 0.103.0, the default-on "Safe import" filter does not sanitize note titles, and the GeoMap note view interpolates a marker note's title into raw HTML that is rendered as innerHTML, allowing an…
When was the CVE record for CVE-2026-48996 published?
The CVE record for CVE-2026-48996 was published on August 27, 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 October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-48996 actively exploited?
CVE-2026-48996 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48996?
CVE-2026-48996 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-48996?
The CVE record for CVE-2026-48996 names the fix: "This issue is fixed in version 0.104.0."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48996?

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