{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11876 exists.","fix":"No fix has been published for CVE-2026-11876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11876 is a medium-severity missing authorization vulnerability in zenml-io/zenml, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-11876 and fix it if it is affected.\n\nWhat it is: CVE-2026-11876 is a medium-severity missing authorization vulnerability in zenml-io/zenml, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11876 exists.\n\nAffected product: zenml-io/zenml. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-11876/ (Markdown: https://insights.sbomify.com/CVE-2026-11876/index.md)","id":"CVE-2026-11876","markdown":"https://insights.sbomify.com/CVE-2026-11876/index.md","name":"CVE-2026-11876","record":{"aliases":["GHSA-7jmq-cfcx-7mr9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ZenML MLOps platform","requires_auth":"low_privilege","summary":"An authenticated user can bypass RBAC checks to enumerate all deployed stacks and sensitive infrastructure details across all tenants in ZenML.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Missing Authorization in get_deployed_stack Endpoint in zenml-io/zenml","id":"CVE-2026-11876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authorization Vulnerability in OpenText Access Manager","id":"CVE-2026-11877"},"packages":[],"prev":{"headline":"WP Support Plus Responsive Ticket System \u003c= 9.1.2 - Unauthenticated Support Ticket Access via Session Cookie Forgery","id":"CVE-2026-11875"},"products":["zenml-io/zenml"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["zenml-io"]},"summary":"An authenticated user can bypass RBAC checks to enumerate all deployed stacks and sensitive infrastructure details across all tenants in ZenML.","url":"https://insights.sbomify.com/CVE-2026-11876/"}