dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-15044

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TrustyAI Service Operator has a missing authentication vulnerability where services like gorch and NemoGuardrails can be deployed with communication channels that don't require authentication if a specific security setting is not enabled. This allows any program within the Kubernetes cluster to access these AI guardrails and orchestrator services without proper authorization, potentially exposing sensitive information and allowing limited modifications to AI models.

MitigationEnable the required security setting (likely authentication/mTLS) when deploying TrustyAI services to ensure all inter-service communication within the cluster requires proper authentication and authorization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if TrustyAI Service Operator is installed
    Run 'kubectl get pods -A | grep -i trusty' or check for trustyai-operator in the list of installed operators if using OLM
    Affected if The TrustyAI Service Operator is present in the cluster and no authentication is enforced on gorch or NemoGuardrails services
  2. Check for running gorch or NemoGuardrails services
    Run 'kubectl get pods -A | grep -E "gorch|nemoguardrails"' to see if these AI services are deployed
    Affected if Either gorch or NemoGuardrails pods are running without authentication configured
  3. Inspect the security configuration of TrustyAI services
    Check the Custom Resource Definitions (CRDs) for TrustyAI services - look for authentication, mTLS, or security settings in the spec. Run 'kubectl get <trusty-service-crds> -A -o yaml' and examine security-related fields
    Affected if The service configuration lacks authentication or mTLS settings, or these settings are explicitly disabled
  4. Verify network access controls
    Check for Kubernetes NetworkPolicies that restrict access to trustyai-related services. Run 'kubectl get networkpolicies -A' and inspect any policies affecting gorch or NemoGuardrails
    Affected if No NetworkPolicy exists or the policy allows unrestricted access from any pod in the cluster to these services
  5. Check service exposure settings
    Examine the service definition for gorch or NemoGuardrails: 'kubectl get svc -A | grep -E "gorch|nemoguardrails"' then 'kubectl get svc <service-name> -n <namespace> -o yaml' - look for type, ports, and any authentication annotations
    Affected if The service is exposed on ClusterIP or LoadBalancer without authentication mechanisms and without cluster-internal access restrictions

You are affected if TrustyAI Service Operator is installed with gorch or NemoGuardrails services running and the authentication/mTLS security setting is not enabled or is disabled in the service configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable the required security setting (likely authentication/mTLS) when deploying TrustyAI services to ensure all inter-service communication within the cluster requires proper authentication and authorization.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15044 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data