Skip to main content
VulnerabilityPublished

CVE-2025-8850: In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-8850· Low 3.1

Not known to be exploited · CVSS 3.1 Low.

Data as of 29 Oct 2026, 23:19 UTC

CVSS 3.0 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2025

  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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubdanny-avila/librechatpkg:github/danny-avila/librechatOther threatsAffected
  • =0.7.9
Fixed in–

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

AI-suggested

Until a fix is available, restrict direct access to the '/api/auth/2fa/disable' endpoint and ensure backend validation of OTP or backup codes is enforced before disabling 2FA.

Description

In danny-avila/librechat version 0.7.9, an insecure API design flaw in the 2-Factor Authentication (2FA) flow allows authenticated users to disable 2FA without providing a valid OTP or backup code. This occurs because the backend does not properly validate these codes when the '/api/auth/2fa/disable' endpoint is accessed directly. The vulnerability weakens account security but does not lead to full account compromise.

References

Community reviews

Loading reviews…