{"answers":{"affected":"3 open source packages ship an affected version, including backend-ai and backend.ai.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49653 exists.","fix":"No fix has been published for CVE-2025-49653 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-49653 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49653 exists.\n\nAffected packages and fixed versions:\n- backend-ai (PyPI): affected all versions up to 25.3.3; no fix listed\n- backend-ai (PyPI): affected all versions up to 25.3.3; no fix listed\n- backend.ai (PyPI): affected all versions up to 25.3.3; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-49653/ (Markdown: https://insights.sbomify.com/CVE-2025-49653/index.md)","id":"CVE-2025-49653","markdown":"https://insights.sbomify.com/CVE-2025-49653/index.md","name":"CVE-2025-49653","record":{"aliases":["GHSA-hxvr-gg2w-j48x","PYSEC-2026-1211"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"BackendAI platform","requires_auth":"high_privilege","summary":"Attackers can retrieve user credentials from active sessions in Lablup BackendAI, leading to potential account takeover on the management platform.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HiddenLayer","cpe":[],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Exposure of sensitive data in active sessions in Lablup's BackendAI allows attackers to retrieve credentials for users on the management platform.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Exposure of sensitive Information allows account takeover","id":"CVE-2025-49653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"Keras framework vulnerable to deserialization of untrusted data","id":"CVE-2025-49655"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["25.3.3"],"package":"backend-ai","purl":"pkg:pypi/backend-ai","source":"GHSA-hxvr-gg2w-j48x"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["25.3.3"],"package":"backend-ai","purl":"pkg:pypi/backend-ai","source":"PYSEC-2026-1211"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["25.3.3"],"package":"backend.ai","purl":null,"source":"GHSA-hxvr-gg2w-j48x"}],"prev":{"headline":"Improper access control allows arbitrary account creation","id":"CVE-2025-49652"},"products":["BackendAI"],"published":"2025-06-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-11","vendors":["Lablup"]},"summary":"Attackers can retrieve user credentials from active sessions in Lablup BackendAI, leading to potential account takeover on the management platform.","url":"https://insights.sbomify.com/CVE-2025-49653/"}