CVE-2024-11172VulnerabilityPublished 20 Mar 2025Updated 15 Oct 2025

CVE-2024-11172: danny-avila/librechat · Uncaught Exception

Affects danny-avila/librechatSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.7.6 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score

7.5High

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

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.7.6

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 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

Upgrade danny-avila/librechat to 0.7.6.

Affected software

Product	Affected	Fixed in
GitHubdanny-avila/librechat`pkg:github/danny-avila/librechat`Other threats	Affected <0.7.6	Fixed in 0.7.6

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

AI-suggested

The primary mitigation is to upgrade all instances of danny-avila/librechat to version 0.7.6 or later, where the vulnerability is fixed by adding proper exception handling around the 'checkBan' middleware. Organizations should audit their deployments to identify affected versions and apply patches promptly. Beyond patching, developers and administrators should review middleware and input processing code to ensure all exceptions are caught and handled gracefully to prevent server crashes. Implementing robust input validation and sanitization can reduce the risk of malicious payloads triggering exceptions. Network-level protections such as rate limiting, web application firewalls (WAFs), and intrusion detection systems (IDS) can help detect and block suspicious traffic patterns targeting this vulnerability. Monitoring server logs for repeated crashes or unusual error messages related to 'checkBan' can provide early warning signs of exploitation attempts. Finally, organizations should incorporate this vulnerability into their incident response plans and conduct regular backups to minimize downtime impact.

Description

A vulnerability in danny-avila/librechat version git a1647d7 allows an unauthenticated attacker to cause a denial of service by sending a crafted payload to the server. The middleware `checkBan` is not surrounded by a try-catch block, and an unhandled exception will cause the server to crash. This issue is fixed in version 0.7.6.

Impact

For European organizations using danny-avila/librechat, this vulnerability poses a significant risk to service availability. A successful attack can cause server crashes, leading to downtime of chat or communication services that rely on this software. This disruption can affect internal communications, customer support channels, or any real-time collaboration tools integrated with librechat. The lack of authentication requirement lowers the barrier for attackers, increasing the likelihood of opportunistic attacks or automated scanning. Organizations in sectors with high dependency on continuous communication, such as finance, healthcare, and public services, may experience operational interruptions. Additionally, service outages can damage reputation and trust, especially if customers or partners rely on these communication platforms. While no data breach risk is present, the denial of service can indirectly impact business processes and compliance with service-level agreements (SLAs). European entities with limited capacity for rapid incident response or patch management may be more vulnerable to prolonged outages.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:21 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats