# CVE-2026-121734: ZaneOps 1.14.0 before 1.15.2 Cross-Workspace Information Disclosure via ReviewPreviewEnvDeployAPIView


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-r87v-8542-wx9q, GHSA-wx9v-p2rq-5m8q

## What is CVE-2026-121734?

CVE-2026-121734 is a medium-severity vulnerability in zane-ops, published on 3 Nov 2026. 

### Official description

ZaneOps 1.14.0 before 1.15.2 contains an authorization bypass vulnerability that allows any workspace administrator to read another workspace's pending preview environment by querying ReviewPreviewEnvDeployAPIView without project scoping. Attackers can use the project slug and environment name from public fork pull request comments to retrieve plaintext environment variables and preview basic-auth credentials.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-121734?


## How do I fix CVE-2026-121734?

No fix has been published for CVE-2026-121734 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121734 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121734 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121734 and fix it if it is affected.

What it is: CVE-2026-121734 is a medium-severity vulnerability in zane-ops, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121734 exists.

Affected product: zane-ops. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121734/ (Markdown: https://insights.sbomify.com/CVE-2026-121734/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121734
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121734
- OSV: https://osv.dev/vulnerability/CVE-2026-121734

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121734/
Summaries are generated and may contain mistakes; the official description above is the record.