← All security briefings

Attention

Joplin Server 3.7.6 changelog lists four security hardening changes

Identifiers: Joplin-Server-3.7.6-security-release · GHSA-2j3q-h77f-c3pp · GHSA-hh9f-h7x6-m8m3

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

The Joplin Server changelog records server-v3.7.6 as released on 16 November 2026 with four security entries. Commit c934c17 stops returning the message of unexpected errors, such as database errors, to clients and escapes request text in logged error messages. Commit 4360b81 only accepts a delta limit from 1 to 1000. Commit e454395 limits the user listing to non-sensitive fields. Commit 926f9bf sends at most one alert per hour when recovery codes are viewed. No CVE is attached to these changes.

Classification reason: Based on the Joplin Server changelog and commits c934c17, 4360b81, e454395 and 926f9bf, retrieved on 17 November 2026, with the changelog entry dated 16 November 2026. The release tag could not be confirmed through the GitHub API at review time. The two related advisories were published 16 November 2026 and state testing on 3.7.3 and 3.7.2 only. These limits mean the briefing cannot confirm supported image availability, per-item applicability to a given server, or coverage of the separate advisories.

Impact

The four entries are security changes whose individual applicability to any given server is not stated, so they should not be rated up or down as a group. Not returning the text of unexpected errors reduces what a client learns about the backend, and escaping request text in log messages reduces log injection risk. Accepting a delta limit only between 1 and 1000 bounds how many items a single delta request can ask for; it does not describe a byte-size cap or a limit on all sync requests. The user list change means the permission-protected user listing API now returns only id, email, full name, account type and creation and update times. The alert throttle limits recovery-code-view notifications to one per hour. The user list endpoint remains behind its existing permission check; this was not an unauthenticated dump of all users.

Who is affected

This applies only to self-hosted Joplin Server. Joplin desktop and mobile apps and Joplin Cloud are not the subject of this changelog. The changelog does not say which versions introduced each weakness, so do not treat every older server or every client as affected. Separately, two advisories published on 16 November 2026, GHSA-2j3q-h77f-c3pp on API password changes not revoking sessions and GHSA-hh9f-h7x6-m8m3 on recovery code regeneration without re-authentication, were tested only on 3.7.3 and 3.7.2 respectively and list no verified fixed version. The second requires MFA to be enabled and a stolen valid session, and the account password is still needed to log in with a regenerated code, so it is not passwordless initial access. The alert throttle in 3.7.6 is a different change and does not by itself establish a fix for either advisory; whether 3.7.6 covers them is not stated in any reviewed source.

Products and versions

Products and versionsAffectedFixed
Joplin Server Per-change introduced and affected versions are unknown; do not treat every older server or client as affected 3.7.6 is the Server changelog target; supported image availability remains to be confirmed

Exploitation evidence

Exploitation not established. No exploitation activity is described in the changelog, the commits or the two related advisories. The advisories include lab reproduction notes only, and absence of reported abuse is not proof that none has occurred.

Sources: Joplin project, Joplin project, Joplin project, Joplin project, Joplin project

Actions

  1. Confirm with your hosting provider or administrator which Joplin Server version is running and whether an official supported 3.7.6 image or package is actually available for your deployment.
  2. Plan the upgrade as a protected change: back up the database and storage, record the current version, and keep a rollback path.
  3. After upgrading, verify that clients sync correctly and that the MFA recovery code and account recovery workflows still behave as expected.
  4. Review who holds permission to list users, since the listing API is permission-protected and now returns fewer fields.
  5. Track the two separate advisories for an official fix. If you run 3.7.3, treat password changes made through the API as not ending existing sessions until a fix is confirmed; other versions were not tested.

Unknowns

  • Per-change introduced and affected versions are not stated in the changelog or commit messages.
  • The GitHub tag endpoint returned 404 during our check, so availability of a supported 3.7.6 release artifact or container image was not confirmed.
  • Whether 3.7.6 addresses GHSA-2j3q-h77f-c3pp or GHSA-hh9f-h7x6-m8m3 is not claimed by any reviewed source, and the advisories themselves were tested only on 3.7.3 and 3.7.2.

Sources

  • Joplin project · retrieved https://raw.githubusercontent.com/laurent22/joplin/dev/readme/about/changelog/server.md
  • Joplin project · retrieved https://api.github.com/repos/laurent22/joplin/commits/c934c17
  • Joplin project · retrieved https://api.github.com/repos/laurent22/joplin/commits/4360b81
  • Joplin project · retrieved https://api.github.com/repos/laurent22/joplin/commits/e454395
  • Joplin project · retrieved https://api.github.com/repos/laurent22/joplin/commits/926f9bf
  • Joplin project · published · updated · retrieved https://github.com/laurent22/joplin/security/advisories/GHSA-2j3q-h77f-c3pp
  • Joplin project · published · updated · retrieved https://github.com/laurent22/joplin/security/advisories/GHSA-hh9f-h7x6-m8m3

Change history

  1. — Published: Published 17 November 2026 from the Joplin Server changelog entry for 3.7.6 dated 16 November 2026 and the four referenced commits.

Subscribe: RSS feed · JSON Feed · Feed format and fields