{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64703 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64703 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64703 is a medium-severity vulnerability in 1Panel-dev MaxKB, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64703 and fix it if it is affected.\n\nWhat it is: CVE-2025-64703 is a medium-severity vulnerability in 1Panel-dev MaxKB, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64703 in the wild and no public exploit code.\n\nAffected product: 1Panel-dev MaxKB. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-64703/ (Markdown: https://insights.sbomify.com/CVE-2025-64703/index.md)","id":"CVE-2025-64703","markdown":"https://insights.sbomify.com/CVE-2025-64703/index.md","name":"CVE-2025-64703","record":{"aliases":["GHSA-qwvm-x4xh-g2qq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AI assistant platform","requires_auth":"low_privilege","summary":"Attackers can leak sensitive information via Python code in the tool module despite sandboxing, affecting enterprise AI assistant deployments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"maxkb","vendor":"maxkb"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"MaxKB is an open-source AI assistant for enterprise. In versions prior to 2.3.1, a user can get sensitive informations by Python code in tool module, although the process run in sandbox. Version 2.3.1 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MaxKB has Information Leak in sandbox","id":"CVE-2025-64703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WebAssembly Micro Runtime vulnerable to a segmentation fault in v128.store instruction","id":"CVE-2025-64704"},"packages":[],"prev":{"headline":"quic-go HTTP/3 QPACK Header Expansion DoS","id":"CVE-2025-64702"},"products":["MaxKB"],"published":"2025-11-13","related":[{"cvss_score":8.8,"headline":"MaxKB vulnerable to privilege escalation through sandbox bypass","id":"CVE-2025-66419","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":8.8,"headline":"MaxKB has a Python sandbox LD_PRELOAD bypass","id":"CVE-2025-66446","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":7.4,"headline":"MaxKB has SSRF in sandbox","id":"CVE-2025-64511","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":6.9,"headline":"MaxKB has Stored XSS via ChatHeadersMiddleware","id":"CVE-2026-39422","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":6.9,"headline":"Stored XSS via Eval Injection in EchartsRander Component","id":"CVE-2026-39423","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":6.8,"headline":"MaxKB RCE vulnerability in function library","id":"CVE-2024-56137","kev_date_added":null,"published":"2025-01-02"},{"cvss_score":6.3,"headline":"MaxKB: Sandbox escape via LD_PRELOAD bypass","id":"CVE-2026-39420","kev_date_added":null,"published":"2026-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-13","vendors":["1Panel-dev"]},"summary":"Attackers can leak sensitive information via Python code in the tool module despite sandboxing, affecting enterprise AI assistant deployments.","url":"https://insights.sbomify.com/CVE-2025-64703/"}