cve.bz

CVE-2026-13451 SSRF

7.7 highEPSS 0.2%

High (7.7). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-13451 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13451?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13451?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-13451 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This Important server-side request forgery (SSRF) flaw in KServe allows an authenticated, low-privileged user with `create/update` permissions on `InferenceService` custom resources to compromise confidentiality. An attacker can leverage a malicious `storageUri` to force the `storage-initializer` init container to issue arbitrary outbound HTTP/HTTPS requests from within the cluster, potentially leading to cloud IAM credential theft or access to internal cluster services. This impacts standard data scientist roles in OpenShift AI / KServe deployments.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-agent-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-autogluon-server-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-controller-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-router-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-storage-initializer-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-13451.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON