{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-39419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-39419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-39419 is a low-severity vulnerability in 1Panel-dev MaxKB, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39419 and fix it if it is affected.\n\nWhat it is: CVE-2026-39419 is a low-severity vulnerability in 1Panel-dev MaxKB, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-39419 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-2026-39419/ (Markdown: https://insights.sbomify.com/CVE-2026-39419/index.md)","id":"CVE-2026-39419","markdown":"https://insights.sbomify.com/CVE-2026-39419/index.md","name":"CVE-2026-39419","record":{"aliases":["GHSA-f3c8-p474-xwfv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI assistant platform","requires_auth":"low_privilege","summary":"Authenticated users can bypass sandbox validation and spoof tool execution results in MaxKB, leading to trusted data manipulation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"maxkb","vendor":"maxkb"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"MaxKB is an open-source AI assistant for enterprise. In versions 2.7.1 and below, an authenticated user can bypass sandbox result validation and spoof tool execution results by exploiting Python frame introspection to read the wrapper's UUID from its bytecode constants, then writing a forged result directly to file descriptor 1 (bypassing stdout redirection). By calling sys.exit(0), the attacker terminates the wrapper before it prints the legitimate output, causing the MaxKB service to parse and trust the spoofed response as the genuine tool result. This issue has been fixed in version 2.8.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: Sandbox Result Validation Bypass via Tool Output Spoofing","id":"CVE-2026-39419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"MaxKB: Sandbox escape via LD_PRELOAD bypass","id":"CVE-2026-39420"},"packages":[],"prev":{"headline":"MaxKB: SSRF via sandbox network hook bypass","id":"CVE-2026-39418"},"products":["MaxKB"],"published":"2026-04-14","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":"2026-04-14","vendors":["1Panel-dev"]},"summary":"Authenticated users can bypass sandbox validation and spoof tool execution results in MaxKB, leading to trusted data manipulation.","url":"https://insights.sbomify.com/CVE-2026-39419/"}