LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Tilelang versions 0.1.0 through 0.1.14 may deserialize manipulated kernel-cache data. If an attacker can influence that cache through the remotely reachable, authenticated attack path described by the advisory, they could compromise confidentiality, integrity, and availability. A corrective commit exists, but the source bundle says no official release contains it yet.

Executive priority

Treat as a prompt remediation item for exposed or shared tilelang environments, especially where users can influence kernel-cache contents. Prioritize access restriction and patch evaluation now because no fixed official release is identified. Isolated deployments with trusted cache writers may have lower immediate exposure, but still require inventory and monitoring.

Technical view

CVE-2026-87083 affects KernelCache._load_kernel_from_disk in tilelang/cache/kernel_cache.py. The weakness is classified as improper input validation and unsafe deserialization (CWE-20 and CWE-502). The supplied CVSS v2 score is 6.5 with network reachability, low complexity, and authentication required. Commit 11ec2397fe942e8b422d026af4a03d6e0a55ae6c is identified as the patch.

Likely exposure

Exposure is limited to tile-ai tilelang 0.1.0–0.1.14 deployments using the affected disk kernel cache where an authenticated remote actor can manipulate cache data. The bundle does not establish whether default configurations permit that influence, so deployment-specific cache provenance, permissions, and trust boundaries must be reviewed.

Exploitation context

The source bundle describes a remote attack requiring authentication, but provides no confirmed exploitation evidence. The CVE is not listed in KEV, and exploit maturity is unspecified. A linked submission mentions remote code execution, but the supplied vulnerability description only establishes deserialization and potential confidentiality, integrity, and availability impact.

Researcher notes

The evidence identifies the vulnerable function, affected versions, weakness classes, CVSS v2 vector, and corrective commit. It does not establish the exact attacker-controlled data path, default exposure, released fixed version, or exploitation in the wild. Validate those points against the linked issue, pull request, patch, and future vendor releases.

Mitigation direction

  • Apply commit 11ec2397fe942e8b422d026af4a03d6e0a55ae6c after compatibility testing.
  • Monitor tile-ai guidance for an official release containing the correction.
  • Restrict kernel-cache modification to trusted identities and processes.
  • Reduce remote access to affected services until remediation is deployed.

Validation and detection

  • Inventory tilelang deployments and identify versions 0.1.0 through 0.1.14.
  • Verify whether deployed source includes the identified corrective commit.
  • Confirm who and what can create or modify kernel-cache files.
  • Review relevant access and cache activity for unexpected modifications.
  • Retest cache loading after remediation without using untrusted serialized data.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-87083 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:ND/RL:OF/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
1ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 2.0MediumAV:N/AC:L/Au:S/C:P/I:P/A:P/E:ND/RL:OF/RC:C86.4VulDB
5.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C2.13.4VulDB
5.5CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C2.13.4VulDB
5.1CVSS 4.0MediumCVSS: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——VulDB

Vulnerability scoring details

Base CVSS 4.0 score

5.1Medium
CVSS 4.0 vector shape for CVE-2026-87083Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tile-aitilelang0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.1.10, 0.1.11, 0.1.12, 0.1.13, 0.1.14Listed
Weakness

CWE details

CWE-20CWE-502

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.