Skip to main content
CVE Radar
mediumInfo Disclosure

CVE-2026-126943

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

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.

Published Updated Sources: diced (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

Diced

2 products listed

CVSS base

4.9

medium · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade Zipline to a fixed release (4.6.2). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Affected vendors, products and versions
VendorProductVersionsStatus
Dicedzipline4.2.0 to < 4.6.2Vulnerable
Dicedzipline4.6.2Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

High

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Every CVSS base score collected, by source and version
ScoreVersionSeverityExpl.ImpactSource
6.9CVSS 4.0mediumn/an/adiced (CNA)
4.9CVSS 3.1mediumn/an/adiced (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-532 · Insertion of Sensitive Information into Log File

  • Read Application Data

Mitigation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.

Weakness & attack patterns

  • CWE-532

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-215 · Fuzzing and observing application log data/errors for application mapping

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Zipline.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 4.9 (AV:N)

    Nov 13, 2026 · NVD

  3. Initial · CVE published

    Nov 13, 2026 · NVD

  4. CVE published by MITRE.

    Nov 13, 2026 · SOCRadar CTI

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-126943 is Zipline 4.2.0 before 4.6.2 OAuth2 Client Secret Leakage in Startup Logs, a medium vulnerability affecting Zipline from Diced. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-126943. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-126943. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.9 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.