# CVE-2026-111269: libical through 4.0.6 Heap Out-of-Bounds Read via icalvalue_decode_ical_string

> Attackers can cause crashes or leak heap memory by sending iCalendar data with a trailing backslash, affecting applications using libical.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-108293, BELL-CVE-2026-111269, DEBIAN-CVE-2026-111269, GHSA-qvfg-9jj8-868q, OESA-2026-4550, OESA-2026-4551, OESA-2026-4552, OESA-2026-4553, UBUNTU-CVE-2026-111269

## What is CVE-2026-111269?

CVE-2026-111269 is a medium-severity memory corruption vulnerability in libical, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

libical through 4.0.6 contains a heap-based out-of-bounds read in icalvalue_decode_ical_string() in src/libical/icalvalue.c when decoding input ending in a backslash. Attackers can supply escaped iCalendar text with a trailing backslash, causing the loop to read past the terminator and crash the application or leak adjacent heap memory.

Weakness: CWE-125 (Out-of-bounds Read)

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


## How do I fix CVE-2026-111269?

Apply the vendor's patch.

## Is CVE-2026-111269 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111269 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111269 and fix it if it is affected.

What it is: CVE-2026-111269 is a medium-severity memory corruption vulnerability in libical, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111269 exists.

Affected product: libical. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111269/ (Markdown: https://insights.sbomify.com/CVE-2026-111269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111269
- OSV: https://osv.dev/vulnerability/CVE-2026-111269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111269/
Summaries are generated and may contain mistakes; the official description above is the record.