CVE-2026-41196

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-25154 (ENISA EUVD)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 23, 2026

Last Modified

November 11, 2026

Advisory Details (2)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

Mod security sandbox escape · Advisory · luanti-org/luanti · GitHub

https://github.com/luanti-org/luanti/security/advisories/GHSA-g596-mf82-w8c3
GitHub commit

commit 8a929dfb97aa (luanti-org/luanti)

Fix landed in luanti-org/luanti commit 8a929dfb97aa — awaiting tagged release

https://github.com/luanti-org/luanti/commit/8a929dfb97aa08337f49ba1bb96a56d6557dc896

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuminetest-server (5.6.1+dfsg+~1.9.0mt8+dfsg-4ubuntu0.1~esm1) @ noble2026-11-11ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
luanti5.10.0+dfsg-5
  • every version up to 5.10.0+dfsg-5+deb13u1: fixed in 5.10.0+dfsg-5+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
luanti5.10.0+dfsg-5 ... 5.15.1+dfsg-2 (6 versions)
  • every version up to 5.15.2+dfsg-1: fixed in 5.15.2+dfsg-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 259 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 159 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 21:23 UTCEchelonGraph re-scored
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-11 23:28 UTCEchelonGraph re-scored
  4. 2026-11-11 23:28 UTCVendor advisory
  5. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-11-11 05:05 UTCEchelonGraph re-scored
  7. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-11-10 07:09 UTCEchelonGraph re-scored
  9. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-11-09 09:11 UTCEchelonGraph re-scored
  11. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-11-08 11:16 UTCEchelonGraph re-scored
  13. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-11-07 13:21 UTCEchelonGraph re-scored
  15. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-11-06 07:55 UTCOSV refresh
  17. 2026-11-05 17:31 UTCEchelonGraph re-scored
  18. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-11-04 19:36 UTCEchelonGraph re-scored
  20. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-11-03 21:40 UTCEchelonGraph re-scored
  22. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-11-02 23:46 UTCEchelonGraph re-scored
  24. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-11-02 01:49 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-02 01:49 UTCVendor advisory
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-01 03:54 UTCEchelonGraph re-scored
  4. 2026-11-01 03:54 UTCVendor advisory
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-31 05:59 UTCEchelonGraph re-scored
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-30 08:04 UTCEchelonGraph re-scored
  9. 2026-10-30 08:04 UTCVendor advisory
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-29 10:09 UTCEchelonGraph re-scored
  12. 2026-10-29 10:09 UTCVendor advisory
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-28 12:13 UTCEchelonGraph re-scored
  15. 2026-10-28 12:13 UTCVendor advisory
  16. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-27 14:18 UTCEchelonGraph re-scored
  18. 2026-10-27 14:18 UTCVendor advisory
  19. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-25 18:03 UTCEchelonGraph re-scored
  21. 2026-10-25 18:03 UTCVendor advisory
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-25 14:30 UTCEchelonGraph re-scored
  24. 2026-10-24 19:37 UTCEchelonGraph re-scored
  25. 2026-10-24 19:37 UTCVendor advisory
  26. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-23 21:42 UTCEchelonGraph re-scored
  28. 2026-10-23 21:42 UTCVendor advisory
  29. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-10-22 23:47 UTCEchelonGraph re-scored
  31. 2026-10-22 23:47 UTCVendor advisory
  32. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-10-22 01:49 UTCEchelonGraph re-scored
  34. 2026-10-22 01:49 UTCVendor advisory
  35. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  36. 2026-10-21 03:51 UTCEchelonGraph re-scored
  37. 2026-10-21 03:51 UTCVendor advisory
  38. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-10-20 05:48 UTCEchelonGraph re-scored
  40. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-10-19 07:25 UTCEchelonGraph re-scored
  42. 2026-10-19 07:25 UTCVendor advisory
  43. 2026-10-18 09:22 UTCVendor advisory
  44. 2026-10-18 03:42 UTCEchelonGraph re-scored
  45. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-10-17 10:56 UTCEchelonGraph re-scored
  47. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-10-16 12:31 UTCEchelonGraph re-scored
  49. 2026-10-16 12:31 UTCVendor advisory
  50. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-10-15 14:25 UTCEchelonGraph re-scored
  52. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  53. 2026-10-14 09:06 UTCEchelonGraph re-scored
  54. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  55. 2026-10-13 05:59 UTCEchelonGraph re-scored
  56. 2026-10-13 05:59 UTCVendor advisory
  57. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-10-12 16:08 UTCEchelonGraph re-scored
  59. 2026-10-11 19:51 UTCEchelonGraph re-scored
  60. 2026-10-11 17:04 UTCEchelonGraph re-scored
  61. 2026-10-11 14:30 UTCEchelonGraph re-scored
  62. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  63. 2026-10-11 05:55 UTCOSV refresh
  64. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  65. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  72. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  73. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  74. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  75. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:13:luanti

Frequently asked(5)

What is CVE-2026-41196?
CVE-2026-41196 is a critical-severity vulnerability; its CVE record was published on April 23, 2026. 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…
When was the CVE record for CVE-2026-41196 published?
The CVE record for CVE-2026-41196 was published on April 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-41196 actively exploited?
CVE-2026-41196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41196?
CVE-2026-41196 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-41196?
A fix for CVE-2026-41196 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41196

Explore →

Is Your Infrastructure Affected by CVE-2026-41196?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs