# CVE-2026-15044: Red Hat TrustyAI Service Operator unauthenticated access in AI APIs

Source: https://junglewise.ai/threats/cve-2026-15044-red-hat-trustyai-service-operator-unauthenticated-access-in-ai  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-08. Updated: 2026-07-08  
License: CC BY 4.0 with a link back

CVE-2026-15044 · Severity: medium · CVSS 6.3 · Published 2026-07-08

A security flaw in the TrustyAI Service Operator allows internal network traffic to bypass identity verification when certain AI services are deployed. This means other programs within the same corporate cloud environment could access AI guardrails and orchestrators without permission. An attacker could use this access to view sensitive data or make unauthorized changes to how AI models behave.

## Quick answers

**Is CVE-2026-15044 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-15044 being exploited in the wild.

**How severe is CVE-2026-15044?** Medium severity, with a CVSS score of 6.3, published 8 July 2026.

**Which products and versions are affected?** Red Hat OpenShift AI (RHOAI) rhoai/odh-trustyai-service-operator-rhel9.

**Is there a fix for CVE-2026-15044?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-15044 attacked?** It is attacked from the adjacent network, in a software library.

**Am I affected by CVE-2026-15044?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A vulnerability exists in the TrustyAI Service Operator where the 'RequiresAuth()' function in 'controllers/utils/auth.go' returns false if the 'security.opendatahub.io/enable-auth' annotation is missing. Because there is no CRD default or mutating webhook to enforce this setting, out-of-the-box deployments of services like gorch and NemoGuardrails serve plain HTTP endpoints without authentication or authorization. An attacker with access to a pod within the same cluster can interact with the AI guardrails and orchestrator APIs. This allows for unauthorized data retrieval and limited modification of AI model configurations. The issue is tracked as CVE-2026-15044.

## Affected products

- Red Hat OpenShift AI (RHOAI) rhoai/odh-trustyai-service-operator-rhel9

## Timeline

- 2026-07-08: disclosed: CVE published and reported by Red Hat

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-15044](https://access.redhat.com/security/cve/CVE-2026-15044)
- [https://bugzilla.redhat.com/show_bug.cgi?id=2498039](https://bugzilla.redhat.com/show_bug.cgi?id=2498039)