Skip to main content
VulnerabilityPublished Updated

CVE-2026-16745: CWE-346

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-16745· High 8.8

Not known to be exploited · CVSS 8.8 High : patch Red Hat OpenShift AI 2.25 soon.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat OpenShift AI 2.25Affected–Fixed in–
Red HatRed Hat OpenShift AI 2.25Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.3Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.3Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–

AI-suggested

Red Hat has released updated images for Red Hat OpenShift AI versions 2.25.10 and 3.4.3 that address this vulnerability. Users should upgrade to these versions following the official Red Hat OpenShift AI upgrade documentation to fully apply the errata update and mitigate the risk. Patch status is confirmed by Red Hat advisories RHSA-2026:53261 and RHSA-2026:53262.

Description

A flaw was found in odh-dashboard, the web console component of Red Hat OpenShift AI (RHOAI). Due to incorrect network binding, a malicious actor within the cluster can bypass authentication and impersonate any user by providing an arbitrary access token. This allows an attacker to gain unauthorized access to the Kubernetes API, potentially leading to arbitrary code execution, privilege escalation, or information disclosure.

References

Community reviews

Loading reviews…