# CVE-2026-107170: M17n-lib: null dereference in minput_open_im() after failed m17n_init()

> A null pointer dereference in m17n-lib causes application crashes during input method initialization, leading to denial of service.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107170, GHSA-68gr-gg8g-xpjj, UBUNTU-CVE-2026-107170, openSUSE-SU-2026:12213-1

## What is CVE-2026-107170?

CVE-2026-107170 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in m17n-lib. A partial failure during library initialization can leave an internal driver pointer uninitialized. Under specific error conditions, such as system resource exhaustion or database corruption, an application attempting to open an input method dereferences this null pointer without proper validation. This issue causes the application to crash, resulting in a Denial of Service (DoS).

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-107170?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ibus-typing-booster` | openSUSE:Tumbleweed | All versions | 2.31.2-1.1 |

## How do I fix CVE-2026-107170?

Apply the vendor's patch.

## Is CVE-2026-107170 being exploited?

There is no known exploitation of CVE-2026-107170 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107170 and fix it if it is affected.

What it is: CVE-2026-107170 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107170 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107170/ (Markdown: https://insights.sbomify.com/CVE-2026-107170/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107170
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107170
- OSV: https://osv.dev/vulnerability/CVE-2026-107170

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107170/
Summaries are generated and may contain mistakes; the official description above is the record.