Skip to main content
VulnerabilityPublished Updated

CVE-2026-54738: LemmyNet lemmy · Improper Control of Interaction Frequency

Affects LemmyNet lemmySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.0.0-beta.1 or 0.19.19 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.0-beta.1, 0.19.19
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade lemmy to 1.0.0-beta.1 or 0.19.19; github/LemmyNet/lemmy to 0.19.19.

Affected software

ProductAffectedFixed in
LemmyNetlemmyAffected
  • >=1.0.0-alpha.5 <1.0.0-beta.1
Fixed in
  • 1.0.0-beta.1
LemmyNetlemmyAffected
  • <0.19.19
Fixed in
  • 0.19.19
crates.iogithub/LemmyNet/lemmypkg:cargo/github/LemmyNet/lemmyOther threatsAffected
  • <0.19.19
  • =1.0.0-beta.1
Fixed in
  • 0.19.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in lemmy versions 0.19.19 and 1.0.0-beta.1. Users should upgrade to at least these versions to remediate the issue.

Description

CVE-2026-54738 is a vulnerability in LemmyNet's lemmy software related to improper control of interaction frequency. It allows unauthenticated attackers to bypass rate limiting by spoofing the client IP address in the X-Forwarded-For header. This affects multiple API endpoints including account registration, login, posting, commenting, searching, image uploading, and account import. The issue is fixed in versions 0.19.19 and 1.0.0-beta.1.

References

Community reviews

Loading reviews…