Contrast workload secrets leak to logs on INFO level

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact When the Contrast initializer is configured with a CONTRASTLOGLEVEL of info or debug, the workload secret is logged to stderr and written to Kubernetes logs. Since info is the default setting, this affects all Contrast installations that don't customize their initializers' log level. The following audiences are intended to have access to workload secrets (see https://docs.edgeless.systems/contrast/1.7/architecture/secrets#workload-secrets): Contrast Coordinator (can derive all workload secrets) Contrast Initializer (obtains only the secret configured in the manifest) Seedshare owner (can derive all workload secrets) Workload owner (can update manifests to obtain secrets) This vulnerability allows the following parties unintended access to workload secrets issued by a Coordinator: Kubernetes users with get or list permission on pods/logs. Others with read access to the Kubernetes log storage (most notably, the cloud provider). This vulnerability does not affect scenarios where…

Published by the source

28 May 2025, 14:40 UTC

Last modified by the source

28 May 2025, 14:40 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h5f8-crrq-4pw8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-h5f8-crrq-4pw8

Advisory: Contrast workload secrets leak to logs on INFO level
IDs: GHSA-h5f8-crrq-4pw8
Record: https://patchnext.com/advisories/ghsa-h5f8-crrq-4pw8 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/edgelesssys/contrast 1.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/edgelesssys/contrast: affected <= 1.8.0; fixed in 1.8.1

## Suggested inspection (read-only)
- Go github.com/edgelesssys/contrast: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/edgelesssys/contrast.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h5f8-crrq-4pw8 (GitHub-reviewed advisory GHSA-h5f8-crrq-4pw8 lists affected ranges: Go github.com/edgelesssys/contrast >=0 <=1.8.0)

Commands are suggestions: review each one before running it.