{"id":"CVE-2026-48815","aliases":["CLSA-2026-1791840004","CLSA-2026-1792582435","EUVD-2026-44494","GHSA-52v5-jr5w-gjxr","ROOT-APP-NPM-CVE-2026-48815"],"status":"published","title":"sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced","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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00173,"percentile":0.0682,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-347"],"published":"2026-07-01T19:58:28Z","modified":"2026-10-28T02:31:13Z","fixes":[{"ecosystem":"npm","package":"sigstore","fixed_in":["4.1.1"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:npm","package":"sigstore","fixed_in":["2.3.1-tuxcare.1","1.9.0-tuxcare.1"],"sources":["osv"]},{"ecosystem":"Root:npm","package":"@rootio/sigstore","fixed_in":["3.0.0-root.io.1","2.1.0-root.io.1","1.9.0-root.io.1","1.5.2-root.io.1","4.0.0-root.io.1","3.1.0-root.io.1","2.3.0-root.io.1","4.1.0-root.io.1","2.2.2-root.io.1","2.3.1-root.io.1"],"sources":["osv"]},{"ecosystem":"Root:npm","package":"sigstore","fixed_in":["3.0.0-aikido.1","2.1.0-aikido.1","1.9.0-aikido.1","1.5.2-aikido.1","4.0.0-aikido.1","3.1.0-aikido.1","2.3.0-aikido.1","4.1.0-aikido.1","2.2.2-aikido.1","2.3.1-aikido.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"sigstore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"4.1.0"},{"fixed":"4.1.1"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"sigstore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.3.1-tuxcare.0"},{"fixed":"2.3.1-tuxcare.1"}]}],"versions":["2.3.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"sigstore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.9.0-tuxcare.0"},{"fixed":"1.9.0-tuxcare.1"}]}],"versions":["1.9.0"]},{"source":"osv","ecosystem":"npm","package":"sigstore","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.1.1"}]}]},{"source":"osv","ecosystem":"Root:npm","package":"@rootio/sigstore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-root.io.1"},{"fixed":"2.1.0-root.io.1"},{"fixed":"1.9.0-root.io.1"},{"fixed":"1.5.2-root.io.1"},{"fixed":"4.0.0-root.io.1"},{"fixed":"3.1.0-root.io.1"},{"fixed":"2.3.0-root.io.1"},{"fixed":"4.1.0-root.io.1"},{"fixed":"2.2.2-root.io.1"},{"fixed":"2.3.1-root.io.1"}]}]},{"source":"osv","ecosystem":"Root:npm","package":"sigstore","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-aikido.1"},{"fixed":"2.1.0-aikido.1"},{"fixed":"1.9.0-aikido.1"},{"fixed":"1.5.2-aikido.1"},{"fixed":"4.0.0-aikido.1"},{"fixed":"3.1.0-aikido.1"},{"fixed":"2.3.0-aikido.1"},{"fixed":"4.1.0-aikido.1"},{"fixed":"2.2.2-aikido.1"},{"fixed":"2.3.1-aikido.1"}]}]}],"products":[{"vendor":"sigstore","product":"sigstore-js"}],"references":[{"url":"https://github.com/sigstore/sigstore-js/security/advisories/GHSA-52v5-jr5w-gjxr","tags":["x_refsource_CONFIRM","exploit","advisory","web"]},{"url":"https://github.com/sigstore/sigstore-js/pull/1658","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/sigstore/sigstore-js/commit/7845532f9d17f6f765363dbee82b01bd159fb52b","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/sigstore/sigstore-js/releases/tag/sigstore%404.1.1","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/advisories/GHSA-52v5-jr5w-gjxr"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48815.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48815","tags":["advisory"]},{"url":"https://github.com/sigstore/sigstore-js","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-48815","title":"sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced","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.","status":"published","published":"2026-07-14T20:27:16.925Z","modified":"2026-07-15T12:56:29.848Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T13:50:49.872037Z"}],"euvd":[{"id":"EUVD-2026-44494","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.","status":"published","published":"2026-07-14T20:27:16Z","modified":"2026-07-15T12:56:29Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T18:19:53.226345Z"}],"ghsa":[{"id":"GHSA-52v5-jr5w-gjxr","title":"sigstore's `certificateOIDs` verification constraints are silently dropped and never enforced","description":"### Summary\n\nThe documented `certificateOIDs` option in `sigstore.verify()` is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked.\n\n### Details\n\nThe public verify options include `certificateOIDs` and the documentation says those OID/value pairs “must be present in the certificate’s extension list.” The policy-construction path used by `sigstore.verify()` and `createVerifier()` only copies the SAN and issuer settings into the verification policy and completely ignores `certificateOIDs`.\n\nAs a result, callers can believe they are constraining verification to certificates carrying specific Fulcio or workload-identifying OIDs, while the actual verifier never receives those constraints. Any bundle that satisfies the remaining checks is accepted even if the required OID extensions are absent or mismatched.\n\nThis is reachable from supported usage through the documented `certificateOIDs` verify option.\n\n### PoC\n\n```javascript\nconst { createVerificationPolicy } = require(\"sigstore/dist/config\");\n\nconst policy = createVerificationPolicy({\n  certificateIssuer: \"https://issuer.example\",\n  certificateIdentityEmail: \"victim@example.com\",\n  certificateOIDs: {\n    \"1.2.3.4\": \"required-value\",\n  },\n});\n\nconsole.log(\"certificateOIDs\" in policy, JSON.stringify(policy));\n// false {\"subjectAlternativeName\":\"victim@example.com\",\"extensions\":{\"issuer\":\"https://issuer.example\"}}\n```\n\n### Impact\n\nApplications that rely on `certificateOIDs` to restrict which certificates may sign artifacts receive no such protection. Unauthorized certificates that should be rejected on extension policy can be accepted as long as they satisfy the remaining verification checks.","status":"published","published":"2026-07-01T19:58:28Z","modified":"2026-07-01T19:58:29Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:40:36.577366Z"}],"nvd":[{"id":"CVE-2026-48815","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.","status":"published","published":"2026-07-14T21:17:01.37Z","modified":"2026-10-24T21:10:00.13Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:12:29.879716Z"}],"osv":[{"id":"CVE-2026-48815","title":"sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced","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.","status":"published","published":"2026-07-14T20:27:16.925Z","modified":"2026-10-28T02:31:13.784176879Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:45:06.701612Z"},{"id":"GHSA-52v5-jr5w-gjxr","title":"sigstore's `certificateOIDs` verification constraints are silently dropped and never enforced","description":"### Summary\n\nThe documented `certificateOIDs` option in `sigstore.verify()` is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked.\n\n### Details\n\nThe public verify options include `certificateOIDs` and the documentation says those OID/value pairs “must be present in the certificate’s extension list.” The policy-construction path used by `sigstore.verify()` and `createVerifier()` only copies the SAN and issuer settings into the verification policy and completely ignores `certificateOIDs`.\n\nAs a result, callers can believe they are constraining verification to certificates carrying specific Fulcio or workload-identifying OIDs, while the actual verifier never receives those constraints. Any bundle that satisfies the remaining checks is accepted even if the required OID extensions are absent or mismatched.\n\nThis is reachable from supported usage through the documented `certificateOIDs` verify option.\n\n### PoC\n\n```javascript\nconst { createVerificationPolicy } = require(\"sigstore/dist/config\");\n\nconst policy = createVerificationPolicy({\n  certificateIssuer: \"https://issuer.example\",\n  certificateIdentityEmail: \"victim@example.com\",\n  certificateOIDs: {\n    \"1.2.3.4\": \"required-value\",\n  },\n});\n\nconsole.log(\"certificateOIDs\" in policy, JSON.stringify(policy));\n// false {\"subjectAlternativeName\":\"victim@example.com\",\"extensions\":{\"issuer\":\"https://issuer.example\"}}\n```\n\n### Impact\n\nApplications that rely on `certificateOIDs` to restrict which certificates may sign artifacts receive no such protection. Unauthorized certificates that should be rejected on extension policy can be accepted as long as they satisfy the remaining verification checks.","status":"published","published":"2026-07-01T19:58:28Z","modified":"2026-09-10T03:50:12.262541909Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:46:37.864461Z"},{"id":"CLSA-2026-1791840004","title":"TuxCare security update for sigstore (1 CVE)","description":"TuxCare rebuilt sigstore to address 1 CVE. Fixed in 2.3.1-tuxcare.1.","status":"published","published":"2026-10-12T21:20:04Z","modified":"2026-10-15T09:47:53.477497965Z","updated_at":"2026-11-02T15:43:50.599064Z"},{"id":"CLSA-2026-1792582435","title":"TuxCare security update for sigstore (1 CVE)","description":"TuxCare rebuilt sigstore to address 1 CVE. Fixed in 1.9.0-tuxcare.1.","status":"published","published":"2026-10-21T11:33:55Z","modified":"2026-10-21T14:00:24.237569148Z","updated_at":"2026-11-02T15:43:54.672859Z"},{"id":"ROOT-APP-NPM-CVE-2026-48815","title":"CVE-2026-48815 in @rootio/sigstore - Patched by Root","description":"Root has patched CVE-2026-48815 in the @rootio/sigstore package for Root:npm. Multiple fixed versions available.","status":"published","published":"2026-07-07T04:07:37Z","modified":"2026-07-07T07:00:04.36773046Z","updated_at":"2026-11-02T15:53:27.649662Z"}]}}