Edgeless Systems Contrast credential leak via unanchored suffix matching in Imagepuller

Severity: low · CVSS 3.7 · Published 2026-07-01

Edgeless Systems Contrast, a tool for confidential computing, contains a flaw in how it identifies container registries. This vulnerability could allow an attacker to trick the system into sending sensitive login credentials or security configurations to a malicious server that mimics a trusted registry's name. While this could lead to the theft of registry passwords, it does not allow an attacker to modify the software being downloaded.

Technologies: Edgeless Systems Contrast, github.com/edgelesssys/contrast (Go). Vendors: Edgeless Systems, Go.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Low severity, with a CVSS score of 3.7, published 1 July 2026.
Which products and versions are affected?
Edgeless Systems Contrast <= 1.20.0; github.com/edgelesssys/contrast (Go) <= 1.20.0.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?
It is attacked over the network, in a software library.
Am I affected?
Check whether you run Edgeless Systems Contrast or github.com/edgelesssys/contrast (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The `Config.registryFor` function in the Contrast Imagepuller component incorrectly identifies registries using unanchored suffix matching via `strings.HasSuffix`. Because the match does not enforce a boundary (like a dot) between the configured FQDN and the request hostname, a configuration for a trusted registry like 'ghcr.io' would also match an attacker-controlled domain like 'evilghcr.io'. If a pull request is directed to such a sibling domain, the Imagepuller will leak the configured Authorization headers, trust custom CA bundles, or apply 'insecure-skip-verify' settings intended for the trusted registry. The vulnerability is mitigated by the fact that image integrity is still verified by digest, preventing code injection. A fix is available in version 1.21.0 which implements exact label matching.

Affected products

  • Edgeless Systems Contrast <= 1.20.0

Timeline

  • 2026-05-27: disclosed
  • 2026-07-01: advisory: Published to GitHub Advisory Database

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.