{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-66419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-66419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66419 is a high-severity vulnerability in 1Panel-dev MaxKB, published on 11 Dec 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-66419 and fix it if it is affected.\n\nWhat it is: CVE-2025-66419 is a high-severity vulnerability in 1Panel-dev MaxKB, published on 11 Dec 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-66419 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-66419/ (Markdown: https://insights.sbomify.com/CVE-2025-66419/index.md)","id":"CVE-2025-66419","markdown":"https://insights.sbomify.com/CVE-2025-66419/index.md","name":"CVE-2025-66419","record":{"aliases":["GHSA-f9qm-2pxq-fx6c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Enterprise AI assistant","requires_auth":"low_privilege","summary":"Attackers can escape the sandbox and escalate privileges in MaxKB via a race condition in the tool module.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"maxkb","vendor":"maxkb"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"MaxKB is an open-source AI assistant for enterprise. In versions 2.3.1 and below, the tool module allows an attacker to escape the sandbox environment and escalate privileges under certain concurrent conditions. This issue is fixed in version 2.4.0.","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 vulnerable to privilege escalation through sandbox bypass","id":"CVE-2025-66419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Tryton sao allows XSS via an HTML attachment","id":"CVE-2025-66420"},"packages":[],"prev":{"headline":"urllib3 allows an unbounded number of links in the decompression chain","id":"CVE-2025-66418"},"products":["MaxKB"],"published":"2025-12-11","related":[{"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":"total"},"state":"PUBLISHED","updated":"2025-12-18","vendors":["1Panel-dev"]},"summary":"Attackers can escape the sandbox and escalate privileges in MaxKB via a race condition in the tool module.","url":"https://insights.sbomify.com/CVE-2025-66419/"}