CVE-2026-13451: Red Hat OpenShift AI (RHOAI) · Server-Side Request Forgery (SSRF)
Affects Red Hat OpenShift AI (RHOAI)Source CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 28 Oct 2026, 20:29 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-agent-rhel9 | Affected– | Fixed in– |
| Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-autogluon-server-rhel9 | Affected– | Fixed in– |
| Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-controller-rhel9 | Affected– | Fixed in– |
| Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-router-rhel9 | Affected– | Fixed in– |
| Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-storage-initializer-rhel9 | Affected– | Fixed in– |
AI-suggested
Red Hat has published an advisory for CVE-2026-13451. The advisory does not explicitly state that a fix is currently available or provide patch links. Until a fix is released, restrict create/update permissions on InferenceService custom resources to trusted users only to reduce risk. Monitor Red Hat's advisory for updates on patches or mitigations.
Description
CVE-2026-13451 is a Server-Side Request Forgery (SSRF) vulnerability in KServe used by Red Hat OpenShift AI (RHOAI). A namespace-scoped user with create/update permissions on InferenceService custom resources can exploit this by supplying a malicious storageUri. This causes the storage-initializer init container to make arbitrary HTTP/HTTPS requests from inside the cluster, potentially exposing sensitive information such as IAM credentials or internal cluster services.