Skip to content
Sign in Sign up
JA EN FR
SecPulse
Medium 6.5

Vulnerability in Red Hat OpenShift AI

CVE-2026-86332 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-86332 has been found in Red Hat OpenShift AI.
Attackers can target a specific entry point like GET /api/nim-serving/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Red Hat OpenShift AI CVE-2026-86332" on the vendor's site.

CVE-2026-86332 (Red Hat OpenShift AI) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/nim-serving/
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (CWE-862) exists in Red Hat OpenShift AI. Attackers reach the vulnerable code path via GET /api/nim-serving/.

Affected scope

Check the vendor advisory for the affected versions of Red Hat OpenShift AI. Attack surface: GET /api/nim-serving/.

Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

How to fix

Update to the patched release per vendor advisory.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual GET /api/nim-serving/ requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Red Hat OpenShift AI を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromisedetect
    grep 'GET /api/nim-serving/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/nim-serving/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verificationverify
    Replay attack against GET /api/nim-serving/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Red Hat Red Hat OpenShift AI 3.5 — —
Red Hat Red Hat OpenShift AI (RHOAI) — —
Red Hat Red Hat OpenShift AI 2.25 — —
Original description The description as published by the source.

A flaw was found in odh-dashboard in Red Hat OpenShift AI. The backend-for-frontend route GET /api/nim-serving/:nimResource reads Kubernetes Secrets using the dashboard service account and returns the full Secret object, including .data, without an authorization check. Any authenticated dashboard user can retrieve the cluster NVIDIA NGC API key Secret (apiKeySecret) and the NIM image pull secret (nimPullSecret). Create and delete of the same NIM credential are admin-gated; the read path is not. This is missing authorization (CWE-862) and insufficiently protected credentials (CWE-522). It is distinct from CVE-2026-5483 (service-account token leak in the Kubernetes client response wrapper on the same route) and CVE-2026-16456 (odh-model-controller cross-namespace confused deputy).

Source: NIST National Vulnerability Database NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details