CVE-2026-111436 · Infrastructure
NO FIX YET
iSulad, a container daemon from openEuler, leaks memory in its mount specification code (specs_mount.c). Repeated triggering exhausts host memory until the daemon runs out of memory and crashes, causing denial of service.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Hosts running the iSulad container daemon through version 2.1.6 are affected. The leak is triggered by requests that go through the mount spec path, so hosts that do not run iSulad can skip it. The sources do not say which request types reach the leaking code.
Not affected if not-using-isulad
Who cares containers, isulad, linux, openeuler
2.1.6 and belowisulad daemon process and its memory growth over time with ps -o rss,cmd -C isuladNo fix yet, per the sources.
Missing release of memory after effective lifetime vulnerability in openEuler iSulad on Linux.
This vulnerability is associated with program file src/daemon/modules/spec/specs_mount.c.
This issue affects iSulad: through 2.1.6.
The memory leak vulnerability causes the iSulad daemon to be triggered frequently, exhausting the host machine's memory and ultimately leading to an OOM crash of the daemon, resulting in a denial of service (DoS).
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.