CVE-2026-54741

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 20, 2026

Advisory Details (7)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

1.0.0-alpha.18

Patch available: LemmyNet/lemmy 1.0.0-alpha.18 (pre-release)

https://github.com/LemmyNet/lemmy/releases/tag/1.0.0-alpha.18
github_release Patch Available

0.19.19

Patch available: LemmyNet/lemmy 0.19.19

https://github.com/LemmyNet/lemmy/releases/tag/0.19.19
github_commit Patch Available

commit 2d169d630b86 (LemmyNet/lemmy)

Patch available: LemmyNet/lemmy 1.0.0-alpha.18 (contains commit 2d169d630b86)

https://github.com/LemmyNet/lemmy/commit/2d169d630b86b9351e4b1dca451214b741f46150
github_commit Patch Available

commit 051b317c9d14 (LemmyNet/lemmy)

Patch available: LemmyNet/lemmy 0.19.19 (contains commit 051b317c9d14)

https://github.com/LemmyNet/lemmy/commit/051b317c9d14b91972bb372c67f319d6900beb93
github_pr Patch Available

[0.19] Don't allow private message edits for blocked users.

Patch available: LemmyNet/lemmy 0.19.19 (PR #6476 merged 2026-04-30)

https://github.com/LemmyNet/lemmy/pull/6476
github_pr Patch Available

Don't allow private message edits for blocked users.

Patch available: LemmyNet/lemmy 1.0.0-alpha.18 (PR #6472 merged 2026-04-29)

https://github.com/LemmyNet/lemmy/pull/6472
github Patch Available🟡 PoC Available

Blocked users can edit private messages sent before the block · Advisory · LemmyNet/lemmy · GitHub

https://github.com/LemmyNet/lemmy/security/advisories/GHSA-46g9-847m-qf8r

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 08:57 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-28 06:38 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 04:12 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 01:54 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 23:37 UTCEG score recompute
  11. 2026-08-23 21:19 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 19:01 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 16:43 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 14:25 UTCEG score recompute
  18. 2026-08-20 13:33 UTCEG score recompute
  19. 2026-08-19 21:20 UTCEG score recompute
  20. 2026-08-19 20:28 UTCEG score recompute
  21. 2026-08-19 20:27 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54741?
CVE-2026-54741 is a medium vulnerability published on August 19, 2026. 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. createprivatemessage checks the recipient's block list with…
When was CVE-2026-54741 disclosed?
CVE-2026-54741 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54741 actively exploited?
CVE-2026-54741 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54741?
CVE-2026-54741 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54741?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54741, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54741?

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

Start Free Scan →Browse All CVEs