A flaw was found in m17n-lib. A user providing specially crafted text input can trigger a heap use-after-free condition during input-method state… (CVE-2026-107167)

The vulnerability in m17n-lib arises from improper handling of an internal input context object during input-method state transitions. Specifically, the library frees this object but later attempts to write to the freed memory, causing a heap use-after-free condition. This can lead to application crashes (denial of service) or potentially arbitrary code execution if exploited. The flaw is triggered by specially crafted text input provided by a user. The affected versions are explicitly enumerated and include several 1.6.x, 1.7.x, and 1.8.x builds.

Applications relying on the vulnerable versions of m17n-lib may crash due to the heap use-after-free condition, resulting in denial of service. Additionally, there is a potential for arbitrary code execution, which could allow an attacker to execute malicious code within the context of the affected application. No known exploits are reported in the wild at this time.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid processing untrusted or specially crafted text input with the affected versions of m17n-lib. Monitor vendor channels for updates and apply patches promptly once released.