Skip to main content
VulnerabilityPublished Updated

CVE-2026-15044: trustyai-service-operator · Missing Authentication

Affects trustyai-service-operatorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.16.3
EPSS
0.2% chance of exploitation in 30 days – higher than 11% 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:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 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 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
TrustyAItrustyai-service-operatorAffected
  • All versions
Fixed in–
GitHubtrustyai-service-operatorpkg:github/trustyai-service-operatorOther threatsAffected
  • All versions
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, ensure that the recommended security setting for TrustyAI Service Operator deployments is enabled to prevent unauthorized access. Follow vendor instructions carefully once provided.

Description

A flaw was found in the TrustyAI Service Operator. When deploying services like gorch or NemoGuardrails, if a specific security setting is not enabled, these services can expose their communication channels without requiring users to prove their identity. This allows any other program within the cluster to access the AI guardrails and orchestrator without proper authorization. An attacker could exploit this to gain unauthorized access to sensitive information and potentially make limited changes to the AI models.

References

Community reviews

Loading reviews…