dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-15063

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 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.

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 gorch service template in trustyai-service-operator exposes orchestrator and detector metrics ports directly on the cluster network without routing through kube-rbac-proxy. This allows any pod to bypass authentication and directly access these metrics endpoints, even when auth is nominally enabled.

MitigationConfigure the gorch service template to remove direct exposure of metrics ports or ensure all traffic must pass through kube-rbac-proxy; implement network policies to restrict access to only authorized proxies.

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 trustyai-service-operator installation
    Run 'kubectl get pods -A | grep trustyai-service-operator' or check operator CSV: 'kubectl get csv -A | grep trustyai-service'
    Affected if The operator is not installed means this CVE does not apply to the environment
  2. Locate the gorch service template
    Check the operator deployment or CRD for the gorch service template configuration. Look for service definitions in the operator's config maps or custom resources: 'kubectl get configmap -A | grep -i gorch' or inspect the TrustyAIService custom resources
    Affected if No gorch service template found means this specific exposure does not exist
  3. Identify exposed metrics ports in the service
    Examine the gorch service definition: 'kubectl get svc -A | grep -i gorch' then describe the service 'kubectl describe svc <gorch-service-name>' to list all exposed ports including orchestrator and detector metrics ports
    Affected if Orchestrator and detector metrics ports are present and directly exposed on the service
  4. Verify if metrics traffic routes through kube-rbac-proxy
    Check if kube-rbac-proxy sidecar exists in pods using the gorch service: 'kubectl get pods -A -o jsonpath={.items[*].spec.containers[*].name} | tr ' ' ' ' | grep rbac-proxy'. Also verify service port targets: 'kubectl get svc <gorch-service-name> -o jsonpath={.spec.ports}' - if ports target metrics endpoints directly instead of proxy, exposure exists
    Affected if Metrics ports are accessible without kube-rbac-proxy authentication (no proxy sidecar or direct port targeting)
  5. Confirm cluster network accessibility
    Test direct access from a non-privileged pod: 'kubectl run test --rm -it --image=curlimages/curl --restart=Never -- curl -s http://<gorch-service>:<metrics-port>/metrics' - if this returns metrics data without auth, the vulnerability is confirmed
    Affected if Any pod in the cluster can retrieve metrics without authentication

The environment is affected if the gorch service exposes orchestrator/detector metrics ports directly on the cluster network without requiring traffic to pass through kube-rbac-proxy for authentication.

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

Configure the gorch service template to remove direct exposure of metrics ports or ensure all traffic must pass through kube-rbac-proxy; implement network policies to restrict access to only authorized proxies.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15063 — 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-15063 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