ISULAD · CVE-2026-111435 · Infrastructure
NO FIX YET
iSulad, the openEuler container runtime daemon, does not sanitize the Config path inside a manifest.json when loading an OCI image. A malicious tar package can make the daemon, which runs as root, read any file on the host.
first public Nov 12, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Hosts running iSulad through 2.1.6 on Linux, especially those that load OCI image tarballs from sources not fully trusted. The sources do not describe a default configuration that makes it exposed, and they do not say whether a remote attacker can deliver a tarball without help.
Not affected if no-untrusted-images, not-using-isulad
Who cares containers, isulad, linux, openeuler, untrusted-image
rpm -q iSulad or isulad --version2.1.6, but no vendor page was read to confirm itisula load on tarballs you did not build yourselfUnknown from the sources.
Relative path traversal vulnerability in openEuler iSulad on Linux.
This vulnerability is associated with program file src/daemon/modules/image/oci/oci_load.c.
This issue affects iSulad: through 2.1.6.
In oci_load.c, oci_load_process_manifest() does not sanitize the Config path of manifest.json. A malicious tar package can enable the isulad with the root permission to read any file on the host.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
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.