{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41196 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-41196 is a critical code injection vulnerability in luanti-org luanti, published on 23 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-41196 and fix it if it is affected.\n\nWhat it is: CVE-2026-41196 is a critical code injection vulnerability in luanti-org luanti, published on 23 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-41196 in the wild and no public exploit code.\n\nAffected product: luanti-org 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-41196/ (Markdown: https://insights.sbomify.com/CVE-2026-41196/index.md)","id":"CVE-2026-41196","markdown":"https://insights.sbomify.com/CVE-2026-41196/index.md","name":"CVE-2026-41196","record":{"aliases":["DEBIAN-CVE-2026-41196","UBUNTU-CVE-2026-41196","USN-8732-1"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Luanti game engine","requires_auth":"low_privilege","summary":"A malicious mod can escape the Lua sandbox to execute arbitrary code and access the filesystem when LuaJIT is enabled.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"minetest","vendor":"minetest"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Luanti (formerly Minetest) is an open source voxel game-creation platform. Starting in version 5.0.0 and prior to version 5.15.2, a malicious mod can trivially escape the sandboxed Lua environment to execute arbitrary code and gain full filesystem access on the user's device. This applies to the server-side mod, async and mapgen as well as the client-side (CSM) environments. This vulnerability is only exploitable when using LuaJIT. Version 5.15.2 contains a patch. On release versions, one can also patch this issue without recompiling by editing `builtin/init.lua` and adding the line `getfenv = nil` at the end. Note that this will break mods relying on this function (which is not inherently unsafe).","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":"Luanti has a mod security sandbox escape","id":"CVE-2026-41196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Brillig: Heap corruption in foreign call results with nested tuple arrays","id":"CVE-2026-41197"},"packages":[],"prev":{"headline":"mosparo: Rule package source URL stored SSRF enables internal HTTP probing","id":"CVE-2026-41195"},"products":["luanti"],"published":"2026-04-23","related":[{"cvss_score":7.7,"headline":"Lua sandbox escape from mod in Minetest","id":"CVE-2022-35978","kev_date_added":null,"published":"2022-08-15"}],"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":"2026-04-23","vendors":["luanti-org"]},"summary":"A malicious mod can escape the Lua sandbox to execute arbitrary code and access the filesystem when LuaJIT is enabled.","url":"https://insights.sbomify.com/CVE-2026-41196/"}