Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 27 Sep 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Edgelesssys
Edgelesssys contrast |
|
| Vendors & Products |
Edgelesssys
Edgelesssys contrast |
Sun, 27 Sep 2026 02:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Contrast (Edgeless Systems) through 1.20.0 performs unanchored suffix matching when selecting per-registry configuration in the imagepuller. Config.registryFor strips a single trailing dot and then uses strings.HasSuffix(hostname, fqdn) without requiring a DNS label boundary, so a registry entry such as [registries."ghcr.io."] is also applied to any host whose name merely ends in that byte sequence, including attacker-registered domains such as evilghcr.io. When an image or layer is pulled from such a sibling domain, the imagepuller sends the configured Authorization header (basic auth, registry token, or identity token), trusts the configured custom CA bundle, follows the configured mirror, and honours insecure-skip-verify (disabling TLS verification) for that host. Image integrity is not affected, as image bytes remain pinned by digest in the policy and are validated after the pull. Configurations that use a leading dot (e.g., [registries.".example.registry"]) are unaffected. | |
| Title | Edgeless Systems Contrast through 1.20.0 Credential Leak via Registry Suffix Matching | |
| Weaknesses | CWE-1289 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-09-27T01:30:05.443Z
Reserved: 2026-09-26T23:23:03.410Z
Link: CVE-2026-100837
No data.
Status : Received
Published: 2026-09-27T02:17:21.937
Modified: 2026-09-27T02:17:21.937
Link: CVE-2026-100837
No data.
OpenCVE Enrichment
Updated: 2026-09-27T11:42:48Z
-
CWE-1289
Improper Validation of Unsafe Equivalence in Input