{"answers":{"affected":"2 open source packages ship an affected version, including @sigstore/oci.","exploited":"There is no known exploitation of CVE-2026-59891 in the wild and no public exploit code.","fix":"Upgrade @sigstore/oci to 0.7.1 or later.","what":"CVE-2026-59891 is a critical vulnerability in sigstore-js, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59891 and fix it if it is affected.\n\nWhat it is: CVE-2026-59891 is a critical vulnerability in sigstore-js, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-59891 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @sigstore/oci (npm): affected all versions; fixed in 0.7.1\n- @sigstore/oci (npm): affected all versions; fixed in 0.7.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59891/ (Markdown: https://insights.sbomify.com/CVE-2026-59891/index.md)","id":"CVE-2026-59891","markdown":"https://insights.sbomify.com/CVE-2026-59891/index.md","name":"CVE-2026-59891","record":{"aliases":["GHSA-pf56-329r-95rw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript Sigstore library","requires_auth":"none","summary":"An attacker can leak registry credentials by exploiting substring matching in credential selection, allowing access to sensitive authentication data.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 0.7.1, getRegistryCredentials() reads credentials from the Docker config file and selects an entry by checking whether any configured auth key contains the target registry string. 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. This issue is fixed in version 0.7.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-07-28","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-28T12:15:55Z","kind":"github_poc","ref":"https://github.com/gyubin02/cve-2026-59891-control-lab","stars":0,"title":"Isolated regression and security-control lab for CVE-2026-59891 in @sigstore/oci"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Credential confusion in @sigstore/oci can leak registry credentials to an attacker-controlled registry","id":"CVE-2026-59891","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"OpenTelemetry JavaScript: Denial of service in `JaegerPropagator` via unhandled exception on a malformed header","id":"CVE-2026-59892"},"packages":[{"ecosystem":"npm","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"@sigstore/oci","purl":null,"source":"GHSA-pf56-329r-95rw"},{"ecosystem":"npm","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"@sigstore/oci","purl":"pkg:npm/%40sigstore/oci","source":"GHSA-pf56-329r-95rw"}],"prev":{"headline":"setuptools: MANIFEST.in exclusion bypass in sdist via Unicode normalization collision (NFC/NFD) on macOS APFS/HFS+","id":"CVE-2026-59890"},"products":["sigstore-js"],"published":"2026-07-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["sigstore"]},"summary":"An attacker can leak registry credentials by exploiting substring matching in credential selection, allowing access to sensitive authentication data.","url":"https://insights.sbomify.com/CVE-2026-59891/"}