CyberSecBulletin
CVE-2025-71425NVD status: Deferred

contrast: Insertion of Sensitive Information into Log File

CVE-2025-71425 is a high-severity insertion of sensitive information into log file vulnerability in contrast from Edgelesssys, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists version 1.8.1 as the first without the flaw, so updating contrast to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update contrast to 1.8.1 or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Edgelesssyscontrastbefore 1.8.11.8.1

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (vulncheck.com).

Scoring systemScoreSeverityScored by
CVSS 4.08.5HighCNA (vulncheck.com)
CVSS 3.17.3HighCNA (vulncheck.com)

Official description

Contrast (Edgeless Systems) before 1.8.1 logs the workload secret to stderr, and thus to Kubernetes logs, when the Contrast initializer is configured with CONTRAST_LOG_LEVEL set to info or debug. Because info is the default, all installations that do not customize the initializer log level are affected. This exposes workload secrets — normally accessible only to the Contrast Coordinator, the initializer, the seedshare owner, and the workload owner — to Kubernetes users with get or list permission on pods/logs and to anyone with read access to the Kubernetes log storage, such as the cloud provider. Deployments that do not use workload secrets are unaffected.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Our coverage

Other vulnerabilities in contrast

All contrast vulnerabilities

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.