{"answers":{"affected":"2 open source packages ship an affected version, including @sigstore/verify.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48816 exists.","fix":"Upgrade @sigstore/verify to 3.1.1 or later.","what":"CVE-2026-48816 is a medium-severity vulnerability in sigstore-js, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48816 and fix it if it is affected.\n\nWhat it is: CVE-2026-48816 is a medium-severity vulnerability in sigstore-js, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48816 exists.\n\nAffected packages and fixed versions:\n- @sigstore/verify (npm): affected from 3.1.0; fixed in 3.1.1\n- @sigstore/verify (npm): affected from 3.1.0; fixed in 3.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-48816/ (Markdown: https://insights.sbomify.com/CVE-2026-48816/index.md)","id":"CVE-2026-48816","markdown":"https://insights.sbomify.com/CVE-2026-48816/index.md","name":"CVE-2026-48816","record":{"aliases":["CLEANSTART-2026-CI36044","CLEANSTART-2026-FX79373","GHSA-xgjw-pm74-86q4","MINI-395r-q29h-26fm","MINI-7px9-hq5x-xmj2","MINI-mgv9-6769-gvvv","MINI-q6qc-7gcc-fqqw","MINI-xq2f-358v-pcvx","ROOT-APP-NPM-CVE-2026-48816"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript Sigstore library","requires_auth":"low_privilege","summary":"Attackers can manipulate certificate validity and timestamp checks in sigstore-js by supplying untrusted bundles, bypassing data authenticity verification.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.1.1, @sigstore/verify derives a transparency-log timestamp from tlogEntries[].integratedTime for bundle v0.2 inclusionProof-only entries even though the inclusion proof path does not cryptographically bind integratedTime, allowing an attacker who can supply an untrusted bundle to influence certificate validity and timestampThreshold verification decisions. This issue is fixed in version 3.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: Insufficient Verification of Data Authenticity","id":"CVE-2026-48816","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Starlette: Arbitrary HTTP method dispatched to `HTTPEndpoint` attributes via `getattr`","id":"CVE-2026-48817"},"packages":[{"ecosystem":"npm","fixed":["3.1.1"],"introduced":["3.1.0"],"last_affected":[],"package":"@sigstore/verify","purl":null,"source":"GHSA-xgjw-pm74-86q4"},{"ecosystem":"npm","fixed":["3.1.1"],"introduced":["3.1.0"],"last_affected":[],"package":"@sigstore/verify","purl":"pkg:npm/%40sigstore/verify","source":"GHSA-xgjw-pm74-86q4"}],"prev":{"headline":"sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced","id":"CVE-2026-48815"},"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["sigstore"]},"summary":"Attackers can manipulate certificate validity and timestamp checks in sigstore-js by supplying untrusted bundles, bypassing data authenticity verification.","url":"https://insights.sbomify.com/CVE-2026-48816/"}