CyberSecBulletin
CVE-2026-40960NVD status: Awaiting Analysis

Luanti: Always-Incorrect Control Flow Implementation

Published Updated By the CyberSecBulletin desk

CVE-2026-40960 is a high-severity always-incorrect control flow implementation vulnerability in Luanti, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 5.15.2 as the first without the flaw, so updating Luanti to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Luanti to 5.15.2 or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
LuantiLuanti5.0.0 up to, but not including, 5.15.25.15.2

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (mitre.org).

Official description

Luanti 5 before 5.15.2 sometimes allows unintended access to an insecure environment. If at least one mod is listed as secure.trusted_mods or secure.http_mods, then a crafted mod can intercept the request for the insecure environment or HTTP API, and also receive access to it.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Always-Incorrect Control Flow Implementation

The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.

More Always-Incorrect Control Flow Implementation vulnerabilities (CWE-670)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Always-Incorrect Control Flow Implementation vulnerabilities

Spotted an error? Tell us.