Contrast leaks workload secrets 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.

This is the same vulnerability as https://github.com/edgelesssys/contrast/security/advisories/GHSA-h5f8-crrq-4pw8. The original vulnerability had been fixed for release v1.8.1, but the fix was not ported to the main branch and thus not present in releases v1.9.0 ff. Below is a brief repetition of the relevant sections from the first GHSA, where you can find the full details. Impact Workload secrets are visible to Kubernetes users with get or list permission on pods/logs, and thus need to be considered compromised. Since workload secrets are used for encrypted storage and Vault integration, those need to be considered compromised, too. Patches Patches: https://github.com/edgelesssys/contrast/commit/5a5512c4af63c17bb66331e7bd2768a863b2f225 https://github.com/edgelesssys/contrast/commit/cf58026b30c43fe7df91eac5322da02e1725d554 The patches are released with v1.12.2 and v1.13.0 (not yet published). Since the secrets are compromised, Contrast needs to be initialized from scratch.…

Published by the source

28 Aug 2025, 16:46 UTC

Last modified by the source

28 Aug 2025, 16:46 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vxg3-w9rv-rhr2

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

# Patch Next advisory brief: GHSA-vxg3-w9rv-rhr2

Advisory: Contrast leaks workload secrets to logs on INFO level
IDs: GHSA-vxg3-w9rv-rhr2
Record: https://patchnext.com/advisories/ghsa-vxg3-w9rv-rhr2 (revision 1, source checked 26 Oct 2026, 15:10 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.12.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/edgelesssys/contrast: affected >= 1.9.0, <= 1.12.1; fixed in 1.12.2

## 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-vxg3-w9rv-rhr2 (GitHub-reviewed advisory GHSA-vxg3-w9rv-rhr2 lists affected ranges: Go github.com/edgelesssys/contrast >=1.9.0 <=1.12.1)

Commands are suggestions: review each one before running it.