In zenml-io/zenml version 0.94.2, the GET /api/v1/stack-deployment/stack endpoint (get_deployed_stack) lacks proper RBAC authorization checks, allowing any authenticated user to enumerate all deployed stacks across all users and tenants. This includes stack component details, service connector information, and user IDs of stack owners. The vulnerability arises from two issues: missing endpoint-level RBAC checks and the use of a server-side Client() that bypasses the RBAC enforcement layer by directly accessing the database through SqlZenStore. This exposes sensitive information such as infrastructure topology, service connector details, stack ownership, and deployment metadata, potentially enabling cross-tenant reconnaissance and further attacks in multi-tenant ZenML Pro/Cloud deployments.
CVE-2026-11876
This medium-severity CVE scores 5.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.0
- EG Score
- 5.0(low)
- EPSS
- 8.2%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 21, 2026commit 9ad2c65f24de (zenml-io/zenml)
Patch available: zenml-io/zenml 0.95.0 (contains commit 9ad2c65f24de)
https://github.com/zenml-io/zenml/commit/9ad2c65f24ded22a5a98d289d63a7f629b434b61huntr - The world's first bug bounty platform for AI/ML
https://huntr.com/bounties/3b434e02-0ee9-4b5e-a44b-0988b6f074c7Vendor Advisories for CVE-2026-11876(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 4× in last 7d / 4× 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.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:29 UTCEG score recompute
- 2026-07-21 14:39 UTCEG score recompute
- 2026-07-21 14:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-11876?
When was CVE-2026-11876 disclosed?
Is CVE-2026-11876 actively exploited?
What is the CVSS score of CVE-2026-11876?
How do I remediate CVE-2026-11876?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-11876
Is Your Infrastructure Affected by CVE-2026-11876?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.