Skip to main content
VulnerabilityPublished Updated

CVE-2026-15581: Missing Authentication

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-15581· High 8.0

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

Data as of 10 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 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 10 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.4Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.4Affected–Fixed in–
Red HatRed Hat OpenShift AI 3.5Affected–Fixed in–

AI-suggested

Red Hat has published advisories acknowledging the vulnerability and has released updated images for Red Hat OpenShift AI versions 2.25.10 and 3.4.3. However, these advisories indicate that no direct fixes for this CVE are included in these releases yet. Users should monitor Red Hat's official documentation and errata for updated instructions on upgrading their clusters and applying forthcoming patches. If you cannot patch yet, restricting pod network access to the TAS backend API and implementing strict network segmentation may reduce exposure.

Description

A flaw was found in the TrustyAI Service (TAS) deployment. This vulnerability allows any pod on the cluster network to bypass authentication and directly access the TAS backend API. An attacker can exploit this to read, tamper with, or delete monitoring data and configurations, and inject arbitrary data into the service, potentially disrupting tenant operations.

References

Community reviews

Loading reviews…