Overview
The cybersecurity world is grappling with yet another vulnerability, this time within Lablup’s BackendAI. Specifically, CVE-2025-49652 is an alarming flaw that allows arbitrary users to create user accounts and access private data, even when registration is disabled. Given the ubiquity of Lablup’s BackendAI in various industries, this vulnerability represents a significant risk, potentially leading to system compromise or data leakage. Addressing this issue should be a top priority for all organizations relying on BackendAI to mitigate potential systemic damage.
Vulnerability Summary
CVE ID: CVE-2025-49652
Severity: Critical (9.8 CVSS score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Lablup BackendAI | All versions prior to patch release
How the Exploit Works
The flaw in question, CVE-2025-49652, resides in the registration feature of Lablup’s BackendAI. It is the result of missing authentication, which allows arbitrary users to create user accounts and access private data, even when registration is disabled. This means that an attacker could take advantage of this vulnerability to create an account without any administrative oversight, hence gaining unauthorized access to sensitive user data and potentially compromising the system.
Conceptual Example Code
The exploitation of this vulnerability could be conceptually illustrated with an HTTP request similar to the one below. In this example, the attacker sends a POST request to the registration endpoint with their details, effectively creating a new user account:
POST /register HTTP/1.1
Host: vulnerable-backendai.example.com
Content-Type: application/json
{
"username": "attacker",
"password": "attacker_password",
"email": "attacker@example.com"
}In this scenario, even though the registration feature is ostensibly disabled, the system still processes the request and creates a new user account, granting the attacker access to the system and potentially private data.
Mitigation
To address this vulnerability, users are strongly advised to apply the vendor patch as soon as it is available. In the meantime, the use of a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can serve as a temporary mitigation measure, helping to detect and block malicious attempts to exploit this vulnerability. However, these are only temporary solutions, and applying the vendor patch is the most effective way to permanently fix this vulnerability.