Vulnerability in @sigstore/oci (CVE-2026-59891)
Summary
Vulnerability in @sigstore/oci (CVE-2026-59891). Successful exploitation can lead to full system takeover. Exploitable via cr.io. Mitigation: upgrade to 0.7.1 or later.
Original description
The description as published by the source.
Impact
This is a credential-exposure / credential-confusion issue.
getRegistryCredentials() reads credentials from the Docker config file (~/.docker/config.json) and selects an entry by checking whether any configured auth key contains the target registry string:
Object.keys(dockerConfig.auths || {}).find((key) => key.includes(registry))
Because this is a substring match rather than an exact host match, credentials configured for one registry can be selected for — and transmitted to — a different registry whose hostname has a substring relationship with a configured auth key (for example, an attacker-controlled cr.io matches a configured ghcr.io).
Who is impacted: Any consumer of @sigstore/oci that uploads artifacts to an OCI registry using credentials from a Docker config, where the destination registry/image reference can be influenced by an untrusted party. This includes @actions/attest and the actions/attest, actions/attest-build-provenance, and actions/attest-sbom GitHub Actions when run with push-to-registry: true, where the subject-name input determines the destination registry.
This is classified as a critical vulnerability given the potential, in a theoretical worst-case scenario, to expose long-lived registry credentials. However, in practice, exploitation requires all of the following:
- The Docker config on the host contains credentials for a registry.
- The destination registry/image reference is influe…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59891 has been found in @sigstore/oci.
Attackers can target a specific entry point like cr.io over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade @sigstore/oci to 0.7.1 or later.
If unsure, ask your IT team or search "@sigstore/oci CVE-2026-59891" on the vendor's site.
CVE-2026-59891 (@sigstore/oci) — CWE-522 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: cr.io / ghcr.io / index.docker.io / docker.io
Patched: 0.7.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-522) exists in @sigstore/oci. Attackers reach the vulnerable code path via cr.io without authentication.
Check the vendor advisory for the affected versions of @sigstore/oci. Attack surface: cr.io / ghcr.io / index.docker.io / docker.io.
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.
Update to 0.7.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@sigstore/oci' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@sigstore/oci' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@sigstore/ociを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @sigstore/oci to 0.7.1ステージング環境で 0.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com