Skip to content

← Actionable
High, CVSS 8.0amended

BackendAI vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

CVE-2025-49653GHSA-hxvr-gg2w-j48x

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI backend-ai

    Affected
    <= 25.3.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.0 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2025-49653: 0.35% estimated exploitation activity in the next 30 days; percentile 28.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Exposure of sensitive data in active sessions in Lablup's BackendAI allows attackers to retrieve credentials for users on the management platform. NOTE: The maintainers of BackendAI do not consider this report to fit with their threat model and advise users to follow security advice from https://github.com/lablup/backend.ai/pull/7587 in their instances to protect themselves from the conditions that would lead to the situation described in the CVE record.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-hxvr-gg2w-j48x

  2. Revision 1 · created ·

    Published from osv record GHSA-hxvr-gg2w-j48x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-49653

Advisory: BackendAI vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
IDs: CVE-2025-49653, GHSA-hxvr-gg2w-j48x
Record: https://patchnext.com/advisories/cve-2025-49653 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI backend-ai: affected <= 25.3.3

## Suggested inspection (read-only)
- `python -m pip show backend-ai`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on backend-ai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hxvr-gg2w-j48x (OSV record GHSA-hxvr-gg2w-j48x lists affected ranges: PyPI backend-ai >=0 <=25.3.3)
- Verified: https://github.com/advisories/GHSA-hxvr-gg2w-j48x (GitHub-reviewed advisory GHSA-hxvr-gg2w-j48x lists affected ranges: PyPI backend-ai >=0 <=25.3.3)

Commands are suggestions: review each one before running it.

Loading voting…