{"answers":{"affected":"3 open source packages ship an affected version, including astrbot. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55449 in the wild and no public exploit code.","fix":"Upgrade astrbot to 3.5.18 or later.","what":"CVE-2025-55449 is a high-severity vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55449 and fix it if it is affected.\n\nWhat it is: CVE-2025-55449 is a high-severity vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-55449 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- astrbot (PyPI): affected all versions; fixed in 3.5.18\n- astrbot (PyPI): affected all versions; fixed in 3.5.18\n- astrbot (PyPI): affected all versions; fixed in 3.5.18\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-55449/ (Markdown: https://insights.sbomify.com/CVE-2025-55449/index.md)","id":"CVE-2025-55449","markdown":"https://insights.sbomify.com/CVE-2025-55449/index.md","name":"CVE-2025-55449","record":{"aliases":["GHSA-4m32-cjv7-f425","PYSEC-2026-285"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Python chatbot framework","requires_auth":"none","summary":"AstrBot uses a hardcoded private key for JWT signing, allowing attackers to forge tokens and bypass authentication or take over accounts.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"astrbot","vendor":"astrbot"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"AstrBotDevs AstrBot 3.5.15 has Advanced_System_for_Text_Response_and_Bot_Operations_Tool as the hardcoded private key used to sign a JWT.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2025-11-11","github_poc":2,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-12-10T05:31:57Z","kind":"github_poc","ref":"https://github.com/xhh1h/CVE-2025-55449","stars":3,"title":"CVE-2025-55449 EXP"},{"date":"2025-11-11T13:11:04Z","kind":"github_poc","ref":"https://github.com/Marven11/CVE-2025-55449-AstrBot-RCE","stars":2,"title":"AstrBot老版本RCE"}],"tier":"poc_unverified"},"has_fix":true,"headline":"AstrBot is vulnerable to RCE with hard-coded JWT signing keys","id":"CVE-2025-55449","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2025-55454"},"packages":[{"ecosystem":"PyPI","fixed":["3.5.18"],"introduced":["0"],"last_affected":[],"package":"astrbot","purl":null,"source":"GHSA-4m32-cjv7-f425"},{"ecosystem":"PyPI","fixed":["3.5.18"],"introduced":["0"],"last_affected":[],"package":"astrbot","purl":"pkg:pypi/astrbot","source":"GHSA-4m32-cjv7-f425"},{"ecosystem":"PyPI","fixed":["3.5.18"],"introduced":["0"],"last_affected":[],"package":"astrbot","purl":"pkg:pypi/astrbot","source":"PYSEC-2026-285"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-55444"},"products":["n/a"],"published":"2026-05-08","related":[{"cvss_score":7.5,"headline":"AstrBot contains a directory traversal vulnerability","id":"CVE-2025-57698","kev_date_added":null,"published":"2025-11-07"},{"cvss_score":7.5,"headline":"AstrBot Has Path Traversal Vulnerability in /api/chat/get_file","id":"CVE-2025-48957","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":6.5,"headline":"AstrBot has an arbitrary file read vulnerability in function _encode_image_bs64","id":"CVE-2025-57697","kev_date_added":null,"published":"2025-11-07"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-08","vendors":["n/a"]},"summary":"AstrBot uses a hardcoded private key for JWT signing, allowing attackers to forge tokens and bypass authentication or take over accounts.","url":"https://insights.sbomify.com/CVE-2025-55449/"}