# CVE-2026-87083: tile-ai tilelang Kernel Cache kernel_cache.py KernelCache._load_kernel_from_disk deserialization

> Remote attackers can exploit unsafe deserialization in tilelang's kernel cache to execute arbitrary code, requiring a patch application.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-jgwf-f39x-m88c

## What is CVE-2026-87083?

CVE-2026-87083 is a medium-severity unsafe deserialization vulnerability in tile-ai tilelang, published on 9 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in tile-ai tilelang up to 0.1.14. This impacts the function KernelCache._load_kernel_from_disk of the file tilelang/cache/kernel_cache.py of the component Kernel Cache. Executing a manipulation can lead to deserialization. The attack may be performed from remote. This patch is called 11ec2397fe942e8b422d026af4a03d6e0a55ae6c. Applying a patch is advised to resolve this issue. Based on the release information, the fix has not been included in any official release yet.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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


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

No fix has been published for CVE-2026-87083 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-87083 being exploited?

There is no known exploitation of CVE-2026-87083 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87083 is a medium-severity unsafe deserialization vulnerability in tile-ai tilelang, published on 9 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-87083 in the wild and no public exploit code.

Affected product: tile-ai tilelang. 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-87083/ (Markdown: https://insights.sbomify.com/CVE-2026-87083/index.md)
```

## Sources

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

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