GPU VulnDB

Database/AI/ML frameworks & serving

LLMKube: Model source paths let a namespace user read controller and node files

CVSS 7.7CVE-2026-68903AI/ML frameworks & servingcurated

Impact

Before 0.9.0, the ModelReconciler accepts any absolute path or file:// URI in Model.spec.source. It then copies that file from the controller pod into model storage or, with modelCache enabled (the default), mounts the chosen node file through a HostPath volume. A user confined to one namespace can read the controller's service-account credentials or other node secrets. That breaks namespace isolation on shared inference clusters and can lead on to cluster-wide access through the controller's token.

Who can reach it

An authenticated Kubernetes user who can create or update LLMKube Model and InferenceService resources in any namespace.

What to do

Upgrade the LLMKube operator to 0.9.0 and roll the controller deployment. If an untrusted user could create Model resources, rotate the controller service-account token and any node secrets that may have been exposed. Until patched, restrict who can create Model and InferenceService resources.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.