# CVE-2025-49653: Exposure of sensitive Information allows account takeover

> Attackers can retrieve user credentials from active sessions in Lablup BackendAI, leading to potential account takeover on the management platform.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** GHSA-hxvr-gg2w-j48x, PYSEC-2026-1211

## What is CVE-2025-49653?

CVE-2025-49653 is a high-severity vulnerability in Lablup BackendAI, published on 9 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Exposure of sensitive data in active sessions in Lablup's BackendAI allows attackers to retrieve credentials for users on the management platform.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `backend-ai` | PyPI | All versions to 25.3.3 | None |
| `backend-ai` | PyPI | All versions to 25.3.3 | None |
| `backend.ai` | PyPI | All versions to 25.3.3 | None |

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

No fix has been published for CVE-2025-49653 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49653 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49653 is a high-severity vulnerability in Lablup BackendAI, published on 9 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49653 exists.

Affected packages and fixed versions:
- backend-ai (PyPI): affected all versions up to 25.3.3; no fix listed
- backend-ai (PyPI): affected all versions up to 25.3.3; no fix listed
- backend.ai (PyPI): affected all versions up to 25.3.3; no fix listed

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-49653/ (Markdown: https://insights.sbomify.com/CVE-2025-49653/index.md)
```

## Sources

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

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