Live › vulnerability › CVE-2026-13451
Go to dashboardA user who can create or update InferenceService resources in their namespace can set a malicious storageUri, making the storage-initializer init container send arbitrary HTTP and HTTPS requests from inside the cluster. An attacker can use this to reach internal services and steal the node's IAM role credentials.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 20:35 UTC. All times on this page are UTC.
Clusters running KServe where some namespace-scoped users can create or update InferenceService resources, since those users control the storageUri value that the storage-initializer fetches. Clusters where only trusted administrators can write InferenceService objects are less exposed. The sources do not name affected KServe versions.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in KServe. A namespace-scoped user with create/update permissions on InferenceService custom resources can exploit this vulnerability by providing a malicious storageUri. This Server-Side Request Forgery (SSRF) vulnerability allows the storage-initializer init container to issue arbitrary outbound HTTP/HTTPS requests from inside the cluster. This can lead to information disclosure, including credential theft for the node's Identity and Access Management (IAM) role or access to internal cluster services.
This page as .md · .json · in your agent: get_signal("CVE-2026-13451")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.