Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3

Lemmy may expose private community data through community, saved, liked, and modlog API views

GHSA-95q8-x6r6-672m

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io lemmy_api

    Affected
    <= 0.19.1-rc.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

NOTE: Only affects development version. Summary Lemmy applies private-community checks in PostView and CommentView, but several adjacent API views skip the accepted-follower filter. Bob, a registered user who is not an accepted follower, can read private community sidebar and summary fields. Alice, a former accepted follower, can still read saved and liked private post bodies after she leaves. An unauthenticated visitor can read private community metadata and removed private post names through the modlog. Details CommunityView::read() and CommunityQuery::list() call visiblecommunitiesonly(), but they do not add the private-community filter used by post and comment reads: PersonSavedCombinedQuery::list() and PersonLikedCombinedQuery::list() join communityactions, but they only filter by the requesting person id. They do not require communityactions.followstate = Accepted when the community has visibility = Private. The modlog query returns ListingType::All without a visibility…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-95q8-x6r6-672m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-95q8-x6r6-672m

Advisory: Lemmy may expose private community data through community, saved, liked, and modlog API views
IDs: GHSA-95q8-x6r6-672m
Record: https://patchnext.com/advisories/ghsa-95q8-x6r6-672m (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io lemmy_api: affected <= 0.19.1-rc.1

## Suggested inspection (read-only)
- crates.io lemmy_api: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lemmy_api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-95q8-x6r6-672m (GitHub-reviewed advisory GHSA-95q8-x6r6-672m lists affected ranges: crates.io lemmy_api >=0 <=0.19.1-rc.1)

Commands are suggestions: review each one before running it.

Loading voting…