# CVE-2025-49652: Improper access control allows arbitrary account creation

> Attackers can create arbitrary accounts to access private data in Lablup BackendAI, even when registration is disabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2025
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-ww28-4m4v-cq4j, PYSEC-2026-290

## What is CVE-2025-49652?

CVE-2025-49652 is a critical missing authorization vulnerability in Lablup BackendAI, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authentication in the registration feature of Lablup's BackendAI allows arbitrary users to create user accounts that can access private data even when registration is disabled.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-49652?

5 open source packages ship an affected version, including backend-ai and backend.ai.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `backend-ai` | PyPI | All versions | 25.15.6, 25.19.0rc1 |
| `backend-ai` | PyPI | All versions | 25.15.6 |
| `backend-ai` | PyPI | From 25.16.0rc1 | 25.19.0rc1 |
| `backend.ai` | PyPI | All versions | 25.15.6 |
| `backend.ai` | PyPI | From 25.16.0rc1 | 25.19.0rc1 |

## How do I fix CVE-2025-49652?

Upgrade backend-ai to a fixed version for your release line: 25.15.6 or 25.19.0rc1.

## Is CVE-2025-49652 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49652 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49652 and fix it if it is affected.

What it is: CVE-2025-49652 is a critical missing authorization vulnerability in Lablup BackendAI, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49652 exists.

Affected packages and fixed versions:
- backend-ai (PyPI): affected all versions; fixed in 25.15.6, 25.19.0rc1
- backend-ai (PyPI): affected all versions; fixed in 25.15.6
- backend-ai (PyPI): affected from 25.16.0rc1; fixed in 25.19.0rc1
- backend.ai (PyPI): affected all versions; fixed in 25.15.6
- backend.ai (PyPI): affected from 25.16.0rc1; fixed in 25.19.0rc1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49652/ (Markdown: https://insights.sbomify.com/CVE-2025-49652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49652
- OSV: https://osv.dev/vulnerability/CVE-2025-49652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49652/
Summaries are generated and may contain mistakes; the official description above is the record.