CVE-2026-100837 Details
Description
Contrast (Edgeless Systems) before 1.21.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.
A vulnerability in Contrast (Edgeless Systems) versions through 1.20.0 allows for unanchored suffix matching when selecting per-registry configurations in the imagepuller. The issue arises because the 'Config.registryFor' setting strips a trailing dot and then applies 'strings.HasSuffix' without requiring a DNS label boundary. This means that a registry entry like '[registries."ghcr.io."]' could be applied to any host ending in that byte sequence, including attacker-controlled domains such as evilghcr.io. When an image or layer is pulled from such a domain, the imagepuller transmits the configured Authorization header (basic auth, registry token, or identity token), trusts the custom CA bundle, follows the configured mirror, and honors 'insecure-skip-verify' (disabling TLS verification) for that host. Although this vulnerability leaks authentication credentials and could bypass TLS verification, it does not affect image integrity, as image bytes are validated after being pulled and remain pinned by digest in the policy.
To address this vulnerability, users should configure explicit subdomains in the imagepuller registry settings. A registry entry with a leading dot (e.g., '[registries.".example.registry"]') is unaffected, but entries without a leading dot may be vulnerable. After the vulnerability was disclosed, Contrast updated the registry matching process to require exact label equality, ensuring that each part of the FQDN must match precisely with the corresponding label in the image reference.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 27, 2026CISA-ADP
Assessed Sep 28, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-1289 | Improper Validation of Unsafe Equivalence in Input | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Edgeless Systems Contrast | <= 1.20.0 (semver) |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 20, 2026 | CVE Modified | [email protected] |
| Sep 28, 2026 | CVE Modified | CISA-ADP |
| Sep 27, 2026 | New CVE Received | [email protected] |
Volerion