BackendAI Missing Authentication for Critical FunctionGHSA-ww28-4m4v-cq4j
CRITICALFix: lablup/backend.ai@37fc8f7GHSA-ww28-4m4v-cq4j is a critical-severity (CVSS 9.8) Missing Authentication vulnerability in backend-ai. A fix is available for backend-ai — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-ww28-4m4v-cq4j.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
backend-ai🐍backend-aiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | backend-ai | all versions | 25.15.6pip install --upgrade 'backend-ai==25.15.6' |
| 🐍PyPI | backend-ai | ≥ 25.16.0rc1&&< 25.19.0rc1 | 25.19.0rc1pip install --upgrade 'backend-ai==25.19.0rc1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backend-ai, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update backend-ai to 25.15.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww28-4m4v-cq4j is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-ww28-4m4v-cq4j in your dependencies?
Find it across PyPI, including transitive dependencies.