Quick answers
- Is CVE-2026-111434 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111434 being exploited in the wild.
- How severe is CVE-2026-111434?
- Medium severity, with a CVSS score of 5.6, published 12 November 2026.
- Which products and versions are affected?
- openEuler iSulad through 2.1.6.
- Is there a fix for CVE-2026-111434?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-111434 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-111434?
- Check whether you run openEuler iSulad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A format string vulnerability exists in src/daemon/modules/image/oci/oci_load.c where the iSulad daemon reads and processes stderr output from the isula runtime shim process. If the shim's stderr contains format specifiers (%s, %x, %n, etc.), an attacker could exploit this to leak memory, cause denial of service, or perform arbitrary memory writes. The vulnerability is triggered during container lifecycle operations (create, start, exec, stop) via pipe communication between daemon and shim.
Affected products
- openEuler iSulad through 2.1.6
Timeline
- 2026-11-12: disclosed