Skip to main content
VulnerabilityPublished Updated

CVE-2026-15063: 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.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% 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
trustyai-explainabilitytrustyai-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, consider restricting pod network access to these metrics ports through network policies or other cluster-level controls to limit unauthorized access. Monitor vendor communications for updates on patches or official mitigations.

Description

A flaw was found in the gorch service template, which is part of the trustyai-service-operator. Even when authentication is enabled, the gorch service exposes unproxied orchestrator and detector metrics ports. This allows any pod on the cluster network to directly access these ports, bypassing the kube-rbac-proxy and its authentication mechanisms. This could lead to unauthorized access to the orchestrator and detector metrics.

References

Community reviews

Loading reviews…