CVE-2026-41196: Luanti has a mod security sandbox escape

Published Apr 23, 2026
·
Updated

Last updated 7 September 2026

Other sources

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).

— MITRE

Affected Software

5 affected componentsFixes available
Luanti Luanti>=5.0.0<5.15.2
debian/luanti
5.10.0+dfsg-5+deb13u15.15.2+dfsg-2
Minetest Minetest>=5.0.0<5.15.2
debian/luanti<5.10.0+dfsg-5+deb13u1
5.10.0+dfsg-5+deb13u1
debian/luanti<5.15.2+dfsg-1
5.15.2+dfsg-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/luanti to a version that resolves this vulnerability.

    Fixed in 5.10.0+dfsg-5+deb13u1Fixed in 5.15.2+dfsg-2
  2. Upgrade

    Upgrade debian/luanti to a version that resolves this vulnerability.

    Fixed in 5.10.0+dfsg-5+deb13u1
  3. Upgrade

    Upgrade debian/luanti to a version that resolves this vulnerability.

    Fixed in 5.15.2+dfsg-1
  4. Upgrade

    Upgrade luanti to a version that resolves this vulnerability.

    Fixed in 5.15.2
  5. Configuration

    For release versions where patching without recompiling is needed, edit `builtin/init.lua` and add the line `getfenv = nil` at the end. Note: this will break mods relying on this function.

    Luanti builtin/init.lua (Lua sandbox environment) = Append `getfenv = nil` at the end of builtin/init.lua

Event History

Apr 23, 2026
CVE Published
via MITRE·12:28 AM
Data Sourced
via MITRE·12:28 AM
DescriptionWeakness
Data Sourced
via OSV·12:28 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 12, 2026
Data Sourced
via OSV·09:47 AM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-41196?

CVE-2026-41196 is considered a critical vulnerability due to its ability to allow arbitrary code execution and full filesystem access.

2

How do I fix CVE-2026-41196?

To resolve CVE-2026-41196, upgrade Luanti from any version between 5.0.0 and 5.15.2 to version 5.15.2 or later.

3

What is the exploitability of CVE-2026-41196?

CVE-2026-41196 is highly exploitable as it allows malicious mods to escape the sandboxed Lua environment.

4

Which versions of Luanti are affected by CVE-2026-41196?

CVE-2026-41196 affects Luanti versions 5.0.0 to 5.15.2.

5

Is there a workaround for CVE-2026-41196?

No official workaround is available for CVE-2026-41196; upgrading to a patched version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203