m17n-lib EUVD-2026-94315

Exploitation requires that m17n-lib initialization partially fails specifically so that the internal driver pointer is left uninitialized (null) - the description names system resource exhaustion or input-method database corruption as the triggering error conditions - after which an application that opens an input method dereferences the null pointer. Limiting factors: the attacker needs local context (AV:L), no reliable way to force these rare error states (reflected in AC:H), and impact is confined to an application crash (A:L, C:N/I:N). It only matters on systems that actually use m17n-lib input methods; hosts without input-method usage are not meaningfully exposed.

This is a genuinely low-priority issue, and the signals are consistent rather than conflicting. The CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L, base 2.9) describes a local-only, high-complexity flaw with no confidentiality or integrity impact and only limited availability impact - i.e. an application crash. No EPSS score, KEV listing, or public POC was provided in the input, so exploitation status is 'no public exploit identified at time of analysis.' The high attack complexity is well-justified by the description: the null driver pointer is only dereferenced under atypical error conditions (system resource exhaustion or database corruption during m17n-lib initialization), which an attacker cannot reliably force. There is no SSVC decision data in the input. In short, this is a low-CVSS, low-real-risk robustness/DoS bug, not an urgent security priority; the only caveat is that PR:N implies no authentication is needed to trigger the crash path, but local access and rare triggering conditions sharply limit practical exploitability.

A local attacker or an adverse runtime condition drives the host into resource exhaustion (e.g. memory/file-descriptor pressure) or corrupts the m17n input-method database so that library initialization partially fails and leaves the internal driver pointer null. When an application then attempts to open an input method, it dereferences the null pointer and crashes, denying service to that application. No public exploit code is identified, and the high complexity means the trigger conditions are hard to control deliberately.