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-2025-62364: CWE-59: Improper Link Resolution Before File Access ('Link Following') in oobabooga text-generation-webui

0
Medium
VulnerabilityCVE-2025-62364cvecve-2025-62364cwe-59
Published: Mon Oct 13 2025 (10/13/2025, 20:30:56 UTC)
Source: CVE Database V5
Vendor/Project: oobabooga
Product: text-generation-webui

Description

text-generation-webui is an open-source web interface for running Large Language Models. In versions through 3.13, a Local File Inclusion vulnerability exists in the character picture upload feature. An attacker can upload a text file containing a symbolic link to an arbitrary file path. When the application processes the upload, it follows the symbolic link and serves the contents of the targeted file through the web interface. This allows an unauthenticated attacker to read sensitive files on the server, potentially exposing system configurations, credentials, and other confidential information. This vulnerability is fixed in 3.14. No known workarounds exist.

AI-Powered Analysis

AILast updated: 10/13/2025, 20:38:49 UTC

Technical Analysis

CVE-2025-62364 is a Local File Inclusion (LFI) vulnerability categorized under CWE-59 (Improper Link Resolution Before File Access) found in the open-source project oobabooga's text-generation-webui, a web interface for running Large Language Models. The vulnerability exists in versions up to 3.13 within the character picture upload functionality. Specifically, the application fails to properly validate or sanitize uploaded files that contain symbolic links. An attacker can craft a text file embedding a symbolic link pointing to any arbitrary file path on the server. Upon upload, the application follows the symbolic link and reads the target file's contents, subsequently serving this data through the web interface. This flaw allows an unauthenticated attacker to read sensitive files on the server, potentially exposing critical information such as system configuration files, credential stores, or other confidential data. The vulnerability does not require any privileges or user interaction, making it easier to exploit in environments where the vulnerable version is deployed. The issue was publicly disclosed on October 13, 2025, and fixed in version 3.14 of the software. No known exploits have been reported in the wild, but the medium CVSS score of 6.2 reflects the significant confidentiality impact and ease of exploitation via local access vectors. The lack of workarounds means patching is the primary mitigation strategy.

Potential Impact

For European organizations using oobabooga text-generation-webui versions 3.13 or earlier, this vulnerability poses a significant risk of unauthorized disclosure of sensitive internal files. Exposure of configuration files or credentials could lead to further compromise, including privilege escalation or lateral movement within networks. Organizations deploying this software in research, AI development, or production environments may face confidentiality breaches impacting intellectual property, personal data, or operational security. Since the vulnerability can be exploited without authentication, any exposed instance accessible to attackers—even internally—could be leveraged. This risk is heightened in sectors with strict data protection regulations such as GDPR, where unauthorized data exposure can result in legal and financial penalties. The absence of known exploits in the wild currently limits immediate widespread impact, but the vulnerability's nature makes it a prime target for attackers once discovered. European entities relying on this software should prioritize patching to prevent potential data leaks and maintain compliance with cybersecurity standards.

Mitigation Recommendations

The definitive mitigation is to upgrade oobabooga text-generation-webui to version 3.14 or later, where the vulnerability is fixed. Until upgrade is possible, organizations should restrict access to the upload feature by implementing strict network segmentation and access controls, limiting exposure to trusted users and systems only. Monitoring and logging upload activities can help detect attempts to exploit symbolic link uploads. Employing file integrity monitoring on server directories involved in uploads can alert administrators to suspicious symbolic link creations. Additionally, deploying web application firewalls (WAFs) with custom rules to detect and block symbolic link payloads in uploads may provide temporary protection. Organizations should also review and harden server file permissions to minimize the impact of any unauthorized file reads. Finally, conducting regular security assessments and penetration tests focusing on file upload functionalities will help identify residual risks.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-10-10T14:22:48.203Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ed6345e828b4dd3cbdd2b9

Added to database: 10/13/2025, 8:38:29 PM

Last enriched: 10/13/2025, 8:38:49 PM

Last updated: 10/16/2025, 10:45:46 AM

Views: 35

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats