Security Resilience

CVE-2024-22422

Mintplexlabs Anythingllm ≤ 2024-01-18

Public PoC
Published
19 January 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.010 63th percentile
Risk Priority 62 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-22422 is a high-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Mintplexlabs Anythingllm. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as LLM Application Platforms; in the Other ATLAS/OWASP Terms risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

AnythingLLM is an application that turns any document, resource, or piece of content into context that any LLM can use as references during chatting. In versions prior to commit `08d33cfd8` an unauthenticated API route (file export) can allow attacker to…

more

crash the server resulting in a denial of service attack. The “data-export” endpoint is used to export files using the filename parameter as user input. The endpoint takes the user input, filters it to avoid directory traversal attacks, fetches the file from the server, and afterwards deletes it. An attacker can trick the input filter mechanism to point to the current directory, and while attempting to delete it the server will crash as there is no error-handling wrapper around it. Moreover, the endpoint is public and does not require any form of authentication, resulting in an unauthenticated Denial of Service issue, which crashes the instance using a single HTTP packet. This issue has been addressed in commit `08d33cfd8`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
AnythingLLM is an application that provides document context to LLMs for chatting, functioning as an enterprise AI assistant platform.

Related Threats

CVEs Like This One

CVE-2026-24477Same product: Mintplexlabs Anythingllm
CVE-2024-3570Same product: Mintplexlabs Anythingllm
CVE-2024-3279Same product: Mintplexlabs Anythingllm
CVE-2026-42456Same product: Mintplexlabs Anythingllm
CVE-2024-3149Same product: Mintplexlabs Anythingllm
CVE-2026-5627Same product: Mintplexlabs Anythingllm
CVE-2024-10109Same product: Mintplexlabs Anythingllm
CVE-2026-41318Same product: Mintplexlabs Anythingllm
CVE-2024-0798Same product: Mintplexlabs Anythingllm
CVE-2024-3101Same product: Mintplexlabs Anythingllm

Affected Assets

mintplexlabs
anythingllm
≤ 2024-01-18

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation explicitly exercises unusual conditions to find missing or incorrect checks.

Input validation directly requires checking for unexpected or malformed conditions before they propagate.

Security engineering principles include structured handling of edge cases and exceptions during design.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.15 Logging partial match
finds

Logging can record unhandled exceptions but does not prevent the weakness itself.

finds

Monitoring may detect symptoms of unhandled conditions but does not eliminate the root weakness.

blocks

Secure development life cycle mandates exception handling and input validation that directly prevent missing checks for unusual conditions.

blocks

Application security requirements explicitly call for handling of exceptional conditions and error paths.

blocks

A.8.27 mandates security-by-design principles (fail securely, least privilege, distrust external input, security-oriented design reviews) that reach some but not most CWE-754 cases; many exceptional-condition checks live in low-level code paths outside architecture-level engineering.

prevents

Secure coding standards directly mandate proper checks for exceptional and unusual conditions.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-754, a class-level weakness. Rules are authored against its narrower children: CWE-354.

References