CVE-2026-15063

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-07-08. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available. Sources: redhat.
redhat

2498058 – (CVE-2026-15063) CVE-2026-15063 trustyai-service-operator: TrustyAI Service Operator: Gorch port bypass when auth IS enabled

https://bugzilla.redhat.com/show_bug.cgi?id=2498058
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-15063

Vendor Advisories for CVE-2026-15063(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 11:47 UTCEG score recompute
  3. 2026-07-27 11:47 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 12:28 UTCEG score recompute
  7. 2026-07-26 12:28 UTCGHSA enrichment
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:05 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:30 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 17:02 UTCEPSS rescore
  19. 2026-07-16 10:22 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 11:03 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 11:41 UTCGHSA enrichment
  24. 2026-07-13 22:30 UTCEPSS rescore
  25. 2026-07-13 12:23 UTCGHSA enrichment
Show 9 more
  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-12 13:04 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 13:43 UTCGHSA enrichment
  5. 2026-07-10 14:24 UTCGHSA enrichment
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 15:05 UTCGHSA enrichment
  8. 2026-07-08 15:46 UTCEG score recompute
  9. 2026-07-08 15:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15063?
CVE-2026-15063 is a medium vulnerability published on July 8, 2026. 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…
When was CVE-2026-15063 disclosed?
CVE-2026-15063 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15063 actively exploited?
CVE-2026-15063 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.7% of all scored CVEs.
What is the CVSS score of CVE-2026-15063?
CVE-2026-15063 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-15063?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15063, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15063

Explore →

Is Your Infrastructure Affected by CVE-2026-15063?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.