CVE-2026-49453

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th 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
Elevated

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

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 7.0Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.6.15 and 3.7.2, Joplin accepts synchronized resource metadata whose id or file_extension contains parent-directory or path-separator characters. BaseItem.unserialize() stores the unvalidated fields, resourceFilename() concatenates them into a destination path, and ResourceFetcher writes the attacker-controlled resource blob outside the resource directory during background synchronization. An attacker with write access to a configured sync target or shared notebook can create or overwrite files at an attacker-chosen existing path without user interaction. This issue is fixed in versions 3.6.15 and 3.7.2.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
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 (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-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-30). 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 or medium mission impact; Track* at high (mission-essential systems).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, 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 or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

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

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

September 21, 2026

Last Modified

September 23, 2026

Advisory Details (5)

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

Path traversal in resource sync — silent arbitrary file write outside the resource directory · Advisory · laurent22/joplin · GitHub

https://github.com/laurent22/joplin/security/advisories/GHSA-r24r-gp6h-cwgf
GitHub pull request

All: Improve how resource filenames are determined

Fix merged in laurent22/joplin PR #15672 on 2026-06-12 — awaiting tagged release

https://github.com/laurent22/joplin/pull/15672
GitHub pull request

All: Reject malformed item IDs during sync

Fix merged in laurent22/joplin PR #15540 on 2026-06-20 — awaiting tagged release

https://github.com/laurent22/joplin/pull/15540
GitHub commit

commit 50518073740c (laurent22/joplin)

Fix landed in laurent22/joplin commit 50518073740c — awaiting tagged release

https://github.com/laurent22/joplin/commit/50518073740c4501058e366300b42c2f1925cb05
GitHub commit

commit 18e0b08c282c (laurent22/joplin)

Fix landed in laurent22/joplin commit 18e0b08c282c — awaiting tagged release

https://github.com/laurent22/joplin/commit/18e0b08c282c89ae51612c4eff67af2a45ff5163

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 47× 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-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-31 09:16 UTCEG score recompute
  4. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-25 14:22 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-24 10:37 UTCEG score recompute
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-18 03:34 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-10-17 11:57 UTCEG score recompute
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 46 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-12 16:00 UTCEG score recompute
  3. 2026-10-11 19:43 UTCEG score recompute
  4. 2026-10-11 16:46 UTCEG score recompute
  5. 2026-10-11 14:21 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-11 03:48 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-10 01:49 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-08 23:15 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-08 10:16 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-06 19:15 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-06 06:16 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-05 04:18 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-04 02:12 UTCEG score recompute
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-10-03 00:15 UTCEG score recompute
  24. 2026-10-01 22:15 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  26. 2026-09-30 20:16 UTCEG score recompute
  27. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  28. 2026-09-29 18:18 UTCEG score recompute
  29. 2026-09-29 04:35 UTCEG score recompute
  30. 2026-09-28 15:36 UTCEG score recompute
  31. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  32. 2026-09-28 02:32 UTCEG score recompute
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  34. 2026-09-27 00:33 UTCEG score recompute
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-09-26 11:34 UTCEG score recompute
  37. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-09-24 20:36 UTCEG score recompute
  39. 2026-09-23 18:39 UTCEG score recompute
  40. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-09-23 03:19 UTCEG score recompute
  42. 2026-09-22 14:20 UTCEG score recompute
  43. 2026-09-22 13:36 UTCEG score recompute
  44. 2026-09-21 21:22 UTCEG score recompute
  45. 2026-09-21 20:58 UTCEG score recomputeFirst assessed: 7.0 HIGH
  46. 2026-09-21 20:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49453?
CVE-2026-49453 is a high-severity vulnerability; its CVE record was published on September 21, 2026. Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.6.15 and 3.7.2, Joplin accepts synchronized resource metadata whose id or file_extension contains parent-directory or path-separator characters. BaseItem.unserialize() stores the…
When was the CVE record for CVE-2026-49453 published?
The CVE record for CVE-2026-49453 was published on September 21, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-49453 actively exploited?
CVE-2026-49453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49453?
CVE-2026-49453 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49453?
The CVE record for CVE-2026-49453 names the fix: "This issue is fixed in versions 3.6.15 and 3.7.2."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49453?

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

Book a Demo →Browse All CVEs