CVE-2025-12805 json
Llama-stack-k8s-operator: llama stack service exposed across namespaces due to missing networkpolicy
published 7mo ago modified 4mo ago also EUVD-2025-209086
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
A flaw was found in Red Hat OpenShift AI (RHOAI) llama-stack-operator. This vulnerability allows unauthorized access to Llama Stack services deployed in other namespaces via direct network requests, because no NetworkPolicy restricts access to the llama-stack service endpoint. As a result, a user in one namespace can access another user’s Llama Stack instance and potentially view or manipulate sensitive data.
Patch / fix
- Red Hat Red Hat OpenShift AI 2.25 sha256:1d258fe98c2477e4256a9b936f412f2501fb7ca9e3b810347f9712e0d5ce5c92, sha256:c0d95dfbae20e87113ffb81026d379bb63ad300447df98b27d1bf9a83b084744
Is CVE-2025-12805 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-12805 updated cvss 8.1
llama-stack-k8s-operator: Llama Stack service exposed across namespaces due to missing NetworkPolicy
-
Red Hat OpenShift AI 2.25 rhoai 1770224279, rhoai 1770788315fixed: vendor fix RHSA-2026:2695
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-dashboard-rhel9, rhoai/odh-mod-arch-model-registry-rhel9not affected: component not present
-
Red Hat OpenShift AI 2.25 rhoai 1770053626, rhoai 1770053627, rhoai 1770053694, rhoai 1770053703, rhoai 1770053721, rhoai 1770053723, +99 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 7mo ago
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=2413101 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected products
- Red Hat Red Hat OpenShift AI 2.25
- Red Hat Red Hat OpenShift AI (RHOAI)
Classification
- Weakness
-
- CWE-653 Improper Isolation or Compartmentalization
References
-
bugzilla.redhat.com
/show_bug.cgi?id=2413101
issue-tracking, exploit, vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:2106
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:2695
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2025-12805
vdb-entry, vendor-advisory
Sources
- CVE List CVE-2025-12805
- NVD CVE-2025-12805
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.