# CVE-2025-57798: Joplin has Denial of Service (DoS) via Uncontrolled Resource Allocation through Title Input

> An attacker can cause a denial of service in Joplin by submitting excessively long note titles, leading to memory exhaustion and application crash.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-6jm8-gr87-q69x

## What is CVE-2025-57798?

CVE-2025-57798 is a medium-severity denial of service vulnerability in laurent22 joplin, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-57798?


## How do I fix CVE-2025-57798?

No fix has been published for CVE-2025-57798 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-57798 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57798 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57798 and fix it if it is affected.

What it is: CVE-2025-57798 is a medium-severity denial of service vulnerability in laurent22 joplin, published on 19 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57798 exists.

Affected product: laurent22 joplin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-57798/ (Markdown: https://insights.sbomify.com/CVE-2025-57798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57798
- OSV: https://osv.dev/vulnerability/CVE-2025-57798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-57798/
Summaries are generated and may contain mistakes; the official description above is the record.