{"answers":{"affected":"2 open source packages ship an affected version, including sigstore.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48815 exists.","fix":"Upgrade sigstore to 4.1.1 or later.","what":"CVE-2026-48815 is a high-severity vulnerability in sigstore-js, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48815 and fix it if it is affected.\n\nWhat it is: CVE-2026-48815 is a high-severity vulnerability in sigstore-js, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48815 exists.\n\nAffected packages and fixed versions:\n- sigstore (npm): affected all versions; fixed in 4.1.1\n- sigstore (npm): affected all versions; fixed in 4.1.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-48815/ (Markdown: https://insights.sbomify.com/CVE-2026-48815/index.md)","id":"CVE-2026-48815","markdown":"https://insights.sbomify.com/CVE-2026-48815/index.md","name":"CVE-2026-48815","record":{"aliases":["CLEANSTART-2026-AZ47953","CLEANSTART-2026-YO55047","CLEANSTART-2026-ZU97983","CLSA-2026-1791840004","CLSA-2026-1792582435","GHSA-52v5-jr5w-gjxr","MINI-3ffx-ppx9-53qm","MINI-53jx-p9pj-2m68","MINI-8q5j-7c9p-9qjg","MINI-h3rr-pvpp-pc4f","MINI-jm4c-xmhp-cf6x","MINI-qvw5-9wcf-9622","MINI-wcg2-r8pc-fqwj","ROOT-APP-NPM-CVE-2026-48815"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript Sigstore library","requires_auth":"none","summary":"Applications using sigstore-js with certificateOIDs constraints fail to enforce them, allowing acceptance of unauthorized signing certificates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 4.1.1, the documented certificateOIDs option in sigstore.verify() is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked and applications relying on certificateOIDs to restrict which certificates may sign artifacts can accept unauthorized certificates. This issue is fixed in version 4.1.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced","id":"CVE-2026-48815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"sigstore-js: Insufficient Verification of Data Authenticity","id":"CVE-2026-48816"},"packages":[{"ecosystem":"npm","fixed":["4.1.1"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":null,"source":"GHSA-52v5-jr5w-gjxr"},{"ecosystem":"npm","fixed":["4.1.1"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":"pkg:npm/sigstore","source":"GHSA-52v5-jr5w-gjxr"}],"prev":{"headline":"Network-AI: Empty default secret still authorizes all requests (Incomplete fix for CVE-2026-46701)","id":"CVE-2026-48814"},"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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["sigstore"]},"summary":"Applications using sigstore-js with certificateOIDs constraints fail to enforce them, allowing acceptance of unauthorized signing certificates.","url":"https://insights.sbomify.com/CVE-2026-48815/"}