CVE-2025-57798

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th 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-2025-209900 (ENISA EUVD)Source: ENISA EUVD

5.5EG
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.2%CVSS: 5.5Exploit: 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. Versions 3.6.14 and prior contain a Denial of Service (DoS) vulnerability in the title input functionality due to a lack of proper length validation. This flaw allows an attacker to cause an Out Of Memory (OOM) error and subsequent program termination by inserting an excessively long string into a note's title. This can be triggered either through direct user interface (UI) input or programmatically via the local web service API after compromising an authentication token. There are 2 primary methods of exploitation: via User Interface (UI) Input, and the Local Web Service API. A local user can directly type or paste an extremely long string into the title field when creating or editing a note Joplin runs a local web service (typically on port 41184) that allows programmatic interaction, such as creating or editing notes via HTTP API calls. If an attacker manages to exfiltrate or compromise the user's authentication token (e.g., through malware on the local system, or other local vulnerabilities), they can then send a crafted HTTP POST request to this local API. By including an excessively long string in the title parameter of this request, the application will attempt to allocate an unbounded amount of memory. This issue has been patched in version 3.7.1.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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.2%
EPSS %ILE
5th
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.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 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.2% 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 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

May 19, 2026

Last Modified

July 24, 2026

Advisory Details (2)

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

Denial of Service (DoS) via Uncontrolled Resource Allocation in Joplin Title Input · Advisory · laurent22/joplin · GitHub

https://github.com/laurent22/joplin/security/advisories/GHSA-6jm8-gr87-q69x
GitHub commit

commit 5b8795da446a (laurent22/joplin)

Fix landed in laurent22/joplin commit 5b8795da446a — awaiting tagged release

https://github.com/laurent22/joplin/commit/5b8795da446a5a40c9e212c98b35e368ffce628e

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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 95 of 229 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-57798?
CVE-2025-57798 is a medium-severity vulnerability; its CVE record was published on May 19, 2026. Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Versions 3.6.14 and prior contain a Denial of Service (DoS) vulnerability in the title input functionality due to a lack of proper length validation. This flaw allows an attacker to cause an…
When was the CVE record for CVE-2025-57798 published?
The CVE record for CVE-2025-57798 was published on May 19, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2025-57798 actively exploited?
CVE-2025-57798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-57798?
CVE-2025-57798 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-57798?
The CVE record for CVE-2025-57798 names the fix: "This issue has been patched in version 3.7.1."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-57798

Explore →

Is Your Infrastructure Affected by CVE-2025-57798?

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

Book a Demo →Browse All CVEs