# CVE-2026-126943: Zipline 4.2.0 before 4.6.2 OAuth2 Client Secret Leakage in Startup Logs


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-2h25-m8rf-v86j, GHSA-m4pq-7mr3-263j

## What is CVE-2026-126943?

CVE-2026-126943 is a medium-severity vulnerability in diced zipline, published on 13 Nov 2026. 

### Official description

Zipline from 4.2.0 before 4.6.2 contains an information disclosure vulnerability that logs sensitive environment variable values, such as OAUTH_OIDC_CLIENT_SECRET, without redaction at startup. Attackers with access to system journal or docker logs can obtain OAuth2 client secrets and use them to exchange intercepted OAuth2 callbacks for valid tokens.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-126943 being exploited?

There is no known exploitation of CVE-2026-126943 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126943 is a medium-severity vulnerability in diced zipline, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-126943 in the wild and no public exploit code.

Affected product: diced zipline. 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-126943/ (Markdown: https://insights.sbomify.com/CVE-2026-126943/index.md)
```

## Sources

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

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