Oci - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/oci/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 29 Oct 2026 17:53:20 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgSigstore-js: Registry credential disclosure (CVE-2026-118763)https://feed.craftedsignal.io/briefs/2026-10-sigstore-js-credential-leak/Thu, 29 Oct 2026 17:53:20 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-sigstore-js-credential-leak/The sigstore-js library prior to 0.7.2 fails to validate OCI registry redirect origins in RegistryClient.uploadBlob(), allowing compromised registries to perform unauthorized exfiltration of authentication headers to attacker-controlled hosts.The sigstore-js library, specifically the RegistryClient.uploadBlob() method, contains a vulnerability where it fails to constrain the destination of requests to an OCI registry's specified upload location. An attacker who controls or compromises an OCI registry can return a malicious blob-upload URL. When the library attempts to upload an artifact, it sends a PUT request to the attacker's host, including credentials (bearer tokens, Basic auth, or custom headers) originally intended for the legitimate registry. This vulnerability is a residual issue from CVE-2026-59891, where previous fixes were insufficient to scope credentials to the registry origin. Version 0.7.2 addresses this by isolating credentials and enforcing origin matching.

Impact

Successful exploitation allows for the theft of sensitive authentication credentials, including bearer tokens and Basic credentials used for registry access.

Recommendation

  • Upgrade sigstore-js to version 0.7.2 or later immediately.
  • Review registry interaction logs for instances where attachArtifactToImage() requests result in redirects or cross-origin POST/PUT operations to non-registry domains.
  • If using sigstore-js within CI/CD pipelines, ensure the registry host configuration follows the principle of least privilege and verify that CI secrets are scoped to specific registry endpoints.
]]>highadvisorycredential-theftocisupply-chain-security