Description
Lemmy is a link aggregator and forum for the fediverse. Prior to 0.19.19 and 1.0.0-alpha.18, Lemmy blocks new private messages from a sender after the recipient blocks that sender, but the edit path skips the same block check. create_private_message checks the recipient's block list with PersonActions::read_block before inserting a message, while edit_private_message in crates/api/api_crud/src/private_message/update.rs only checks that the caller is orig_private_message.creator_id. The update then writes new content and returns the modified PrivateMessageView without consulting the recipient's block list, allowing a blocked sender to keep changing an old message that the recipient can still see and providing a post-block harassment path. This issue is fixed in versions 0.19.19 and 1.0.0-alpha.18.
Published: 2026-08-19
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw occurs in the private message update routine, where the block check that prevents new messages is omitted. An attacker who has been blocked by a recipient can continue to edit any private message that was sent before the block. The edit is permitted because the only guard is that the caller is the original creator. The result is that a blocked user can repeatedly modify content that the recipient can still view, creating a harassment or abuse channel. The weakness underlying this is missing access control on privileged operations (CWE-862).

Affected Systems

The vulnerability affects LemmyNet's Lemmy platform. Versions earlier than 0.19.19 of the stable releases and earlier than 1.0.0-alpha.18 of the alpha line are susceptible. All instances running those releases should be considered affected until patched.

Risk and Exploitability

This flaw presents a moderate severity, reflected in the CVSS score of 5.3. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog. An attacker must have a private message relationship and be blocked by the target; once those conditions are met, the block list check is bypassed during edit. The lack of a block verification in the edit path allows repeated modification, making this a viable post‑block harassment vector. The risk remains predominantly in user‑to‑user relationships and does not expose broader system compromise.

Generated by OpenCVE AI on August 20, 2026 at 11:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Lemmy to at least 0.19.19 or 1.0.0‑alpha.18, which contain the fix for the missing block check.
  • Review any custom instance code or configuration that handles private message edits to ensure that the recipient’s block list is consulted during editing; if it is omitted, re‑implement the check.
  • Until the update is applied, consider disabling the edit capability for blocked users or removing privately sent messages that were created before the block to prevent abuse.

Generated by OpenCVE AI on August 20, 2026 at 11:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 20 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 19 Aug 2026 22:45:00 +0000

Type Values Removed Values Added
First Time appeared Lemmynet
Lemmynet lemmy
Vendors & Products Lemmynet
Lemmynet lemmy

Wed, 19 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Description Lemmy is a link aggregator and forum for the fediverse. Prior to 0.19.19 and 1.0.0-alpha.18, Lemmy blocks new private messages from a sender after the recipient blocks that sender, but the edit path skips the same block check. create_private_message checks the recipient's block list with PersonActions::read_block before inserting a message, while edit_private_message in crates/api/api_crud/src/private_message/update.rs only checks that the caller is orig_private_message.creator_id. The update then writes new content and returns the modified PrivateMessageView without consulting the recipient's block list, allowing a blocked sender to keep changing an old message that the recipient can still see and providing a post-block harassment path. This issue is fixed in versions 0.19.19 and 1.0.0-alpha.18.
Title Lemmy: Blocked users can edit private messages sent before the block
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-20T13:21:16.938Z

Reserved: 2026-06-15T23:12:41.964Z

Link: CVE-2026-54741

cve-icon Vulnrichment

Updated: 2026-08-20T13:20:45.790Z

cve-icon NVD

Status : Received

Published: 2026-08-19T21:16:58.510

Modified: 2026-08-20T14:17:14.553

Link: CVE-2026-54741

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T11:30:16Z

Weaknesses