Advisory record · GHSA-jmxc-hhwx-gvv3

Private Lemmy instances expose multi-community metadata without authentication

CVSS 5.3 Medium

Published by the GitHub Advisory Database at 6 May 2026, 22:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
lemmy_apicrates.io<=0.19.1-rc.1No fixed version yet
Identifiers
GHSA-jmxc-hhwx-gvv3
Weakness (CWE)
CWE-862
Published
6 May 2026
Updated
8 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The lemmy_api crate, versions up to and including 0.19.1-rc.1, does not enforce the private-instance setting on its multi-community read handler. An unauthenticated visitor on a private instance can read multi-community names, titles, summaries, sidebars, owner identities and member community lists. The source says this affects only the development version and lists no fixed version.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.