Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24478: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Mintplex-Labs anything-llm

0
High
VulnerabilityCVE-2026-24478cvecve-2026-24478cwe-22
Published: Mon Jan 26 2026 (01/26/2026, 23:23:54 UTC)
Source: CVE Database V5
Vendor/Project: Mintplex-Labs
Product: anything-llm

Description

CVE-2026-24478 is a high-severity path traversal vulnerability in Mintplex-Labs' anything-llm application prior to version 1. 10. 0. It arises from improper restriction of pathnames in the DrupalWiki integration, allowing a malicious admin or an attacker who can manipulate an admin to write arbitrary files on the server. This can lead to remote code execution by overwriting configuration files or deploying executable scripts. The vulnerability requires high privileges (admin access) but no user interaction. The flaw is fixed in version 1. 10. 0. European organizations using affected versions should prioritize patching to prevent potential compromise.

AI-Powered Analysis

AILast updated: 01/27/2026, 19:08:23 UTC

Technical Analysis

CVE-2026-24478 is a critical path traversal vulnerability (CWE-22) found in the DrupalWiki integration component of the Mintplex-Labs anything-llm application, versions prior to 1.10.0. AnythingLLM is designed to convert content into contextual references usable by large language models during chat interactions. The vulnerability stems from improper validation and limitation of file pathnames, allowing an attacker with administrative privileges or the ability to influence an admin to configure a malicious DrupalWiki URL to write arbitrary files anywhere on the server filesystem. This arbitrary file write capability can be exploited to overwrite critical configuration files or deploy malicious executable scripts, leading to remote code execution (RCE). The CVSS v3.1 base score is 7.2, reflecting high impact on confidentiality, integrity, and availability, with network attack vector, low attack complexity, and requiring high privileges but no user interaction. The flaw was publicly disclosed on January 26, 2026, and fixed in version 1.10.0 of anything-llm. Although no known exploits have been reported in the wild, the vulnerability poses a significant risk if leveraged by attackers, especially in environments where anything-llm is deployed with DrupalWiki integration and administrative access is attainable or can be socially engineered.

Potential Impact

For European organizations, exploitation of this vulnerability could result in severe consequences including unauthorized disclosure of sensitive data, full system compromise, and disruption of services. Since the vulnerability allows arbitrary file writes and potential remote code execution, attackers could implant backdoors, manipulate application behavior, or exfiltrate confidential information. Organizations relying on anything-llm for AI-driven content contextualization, especially those integrating DrupalWiki, face risks to both their operational integrity and data confidentiality. The requirement for administrative privileges limits the attack surface but does not eliminate risk, as insider threats or social engineering attacks targeting admins could enable exploitation. The impact is particularly critical for sectors with stringent data protection regulations such as finance, healthcare, and government institutions within Europe, where breaches could lead to regulatory penalties and reputational damage.

Mitigation Recommendations

European organizations should immediately upgrade anything-llm to version 1.10.0 or later to remediate the vulnerability. Until patching is complete, restrict administrative access to trusted personnel only and implement strict access controls and monitoring on admin accounts to detect suspicious configuration changes. Employ network segmentation to isolate systems running anything-llm and DrupalWiki integrations from broader enterprise networks. Conduct thorough audits of existing configurations to identify and remove any malicious or suspicious DrupalWiki URLs. Implement file integrity monitoring to detect unauthorized file writes or modifications. Additionally, enhance security awareness training for administrators to mitigate social engineering risks. Where possible, deploy web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting the DrupalWiki integration endpoints.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-23T00:38:20.547Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69790cec4623b1157c4004a0

Added to database: 1/27/2026, 7:07:24 PM

Last enriched: 1/27/2026, 7:08:23 PM

Last updated: 1/27/2026, 8:14:06 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats