{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-40959 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-40959 is a critical code injection vulnerability in Luanti, published on 16 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40959 and fix it if it is affected.\n\nWhat it is: CVE-2026-40959 is a critical code injection vulnerability in Luanti, published on 16 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40959 in the wild and no public exploit code.\n\nAffected product: Luanti. 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-40959/ (Markdown: https://insights.sbomify.com/CVE-2026-40959/index.md)","id":"CVE-2026-40959","markdown":"https://insights.sbomify.com/CVE-2026-40959/index.md","name":"CVE-2026-40959","record":{"aliases":["DEBIAN-CVE-2026-40959","GHSA-wxm2-x9x9-x5mj","UBUNTU-CVE-2026-40959"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Luanti game engine","requires_auth":"none","summary":"Attackers can execute arbitrary code by exploiting a Lua sandbox escape in Luanti when LuaJIT is enabled via a crafted mod.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"Luanti 5 before 5.15.2, when LuaJIT is used, allows a Lua sandbox escape via a crafted mod.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Code injection in Luanti","id":"CVE-2026-40959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in Luanti","id":"CVE-2026-40960"},"packages":[],"prev":{"headline":"Input validation error in Secure Access clients prior to 14.55","id":"CVE-2026-40958"},"products":["Luanti"],"published":"2026-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-04-16","vendors":["Luanti"]},"summary":"Attackers can execute arbitrary code by exploiting a Lua sandbox escape in Luanti when LuaJIT is enabled via a crafted mod.","url":"https://insights.sbomify.com/CVE-2026-40959/"}