VulnerabilityPublished 30 Oct 2025Updated 5 Nov 2025

CVE-2025-8850: danny-avila/librechat · Expected Behavior Violation

Affects danny-avila/librechatSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.0 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubdanny-avila/librechat`pkg:github/danny-avila/librechat`Other threats	Affected =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

European organizations should immediately audit their deployment of danny-avila/librechat to determine if version 0.7.9 or other vulnerable versions are in use. Until a patch is available, administrators should implement compensating controls such as restricting access to the 2FA disable API endpoint via network-level controls or API gateways. Monitoring and alerting on 2FA disable events can help detect suspicious activity. Enforcing strong password policies and additional authentication layers (e.g., hardware tokens or biometric factors) can reduce risk. User education about the importance of 2FA and recognizing social engineering attempts is critical. Organizations should track updates from the vendor or community for patches addressing this vulnerability and apply them promptly. Additionally, consider integrating external identity providers with stronger 2FA enforcement if feasible. Regular security assessments and penetration testing should include validation of 2FA mechanisms to prevent similar design flaws.

Description

In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint '/api/auth/2fa/disable' is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise.

Impact

For European organizations using danny-avila/librechat, this vulnerability poses a risk of weakened account security. Attackers who gain authenticated access to user accounts can disable 2FA without additional verification, increasing the likelihood of subsequent account compromise through credential theft or phishing. This could lead to unauthorized access to sensitive communications and data. Although the vulnerability does not allow immediate full account takeover, it lowers the barrier for attackers to escalate privileges or move laterally within an organization’s communication infrastructure. The impact is more pronounced in sectors requiring strong authentication controls, such as finance, government, and critical infrastructure. The absence of known exploits reduces immediate risk, but the vulnerability could be targeted in future attacks if left unmitigated. Organizations relying on librechat for secure messaging should consider this a security weakness that undermines multi-factor authentication benefits.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2025, 21:10 UTC

WeaknessesCWE-440

Technical details

References

Community reviews

Related threats