{"answers":{"affected":"3 open source packages ship an affected version, including github.com/sigstore/sigstore-go. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-49834 in the wild and no public exploit code.","fix":"Upgrade github.com/sigstore/sigstore-go to 1.2.0 or later.","what":"CVE-2026-49834 is a medium-severity vulnerability in sigstore-go, published on 17 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-49834 and fix it if it is affected.\n\nWhat it is: CVE-2026-49834 is a medium-severity vulnerability in sigstore-go, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49834 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/sigstore/sigstore-go (Go): affected all versions; fixed in 1.2.0\n- github.com/sigstore/sigstore-go (Go): affected all versions; fixed in 1.2.0\n- github.com/sigstore/sigstore-go (Go): affected all versions; fixed in 1.2.0\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-49834/ (Markdown: https://insights.sbomify.com/CVE-2026-49834/index.md)","id":"CVE-2026-49834","markdown":"https://insights.sbomify.com/CVE-2026-49834/index.md","name":"CVE-2026-49834","record":{"aliases":["CLEANSTART-2026-OE12981","CLEANSTART-2026-OY65007","DEBIAN-CVE-2026-49834","GHSA-9vcr-p3rj-q5q6","GO-2026-5952","MINI-24c8-8xp2-pcj5","MINI-25j4-q633-5wq2","MINI-2x3f-qfh9-8fhv","MINI-3vpw-656g-q24w","MINI-4333-3gvm-24wc","MINI-445f-pjp9-4vhj","MINI-47mq-g227-8qw9","MINI-4xjr-r2pg-cff6","MINI-53wf-rq5f-rg3g","MINI-684q-249f-682v","MINI-6j64-c946-786c","MINI-6m8f-xw37-fwc6","MINI-6qhm-c8f7-5j2h","MINI-6rvh-c86p-fx3q","MINI-6vxf-j7hp-425w","MINI-6wvq-vxvh-q3hm","MINI-74pj-rhcg-phrm","MINI-7ghg-47rj-8m7r","MINI-84cf-g2jf-mmgm","MINI-85r6-3qrv-h68h","MINI-898q-fq4q-j7h4","MINI-89vm-w5qw-q47x","MINI-8mf8-wgqc-q4g6","MINI-993w-q5cf-cj32","MINI-9cc3-wc7x-w59v","MINI-c325-v74g-f28h","MINI-c73f-3chh-5qq7","MINI-c7f8-335j-mm7f","MINI-chwg-w7wq-whgh","MINI-cwjg-4h25-57rm","MINI-g4q5-vp6r-w683","MINI-g56x-fjvp-2gm8","MINI-gfh8-pjr5-ghcm","MINI-gh5h-96v6-5mr5","MINI-gvq8-xgwr-hjm7","MINI-h2jw-2h37-6hc8","MINI-h524-v54v-wrg8","MINI-h6m4-4h3w-22xp","MINI-h86f-g9xv-9q55","MINI-hq48-wq3h-p3q8","MINI-hvc9-ph84-p8x8","MINI-j54f-fg72-9f57","MINI-j646-gc5c-f6pm","MINI-jhv6-v5q8-33jp","MINI-jp24-44r5-pg2h","MINI-mh3p-pfrc-h598","MINI-mp6q-wfmm-3vg9","MINI-ppx4-44m8-rpmj","MINI-prq3-6399-m4rj","MINI-q4xx-3g26-fqpf","MINI-q97w-vx9j-mxhg","MINI-qfpw-jpvm-7q3g","MINI-qm36-p858-6rph","MINI-r5g8-r9r5-rxpp","MINI-rqwp-rhp7-7r79","MINI-rxh5-622f-5g2q","MINI-v84p-4267-jpxj","MINI-vjcg-548w-m76p","MINI-vr27-3mj3-88qp","MINI-vv96-9vcq-qxv7","MINI-w6f7-jp3c-8478","MINI-w6qg-fqrf-85w7","MINI-w873-w5f3-rjhx","MINI-wmwh-x878-qm32","MINI-wp69-75wv-hvcg","MINI-wqr3-63m9-g2fg","MINI-x386-xcqj-739w","MINI-xwqj-72jw-hhm4","UBUNTU-CVE-2026-49834"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Go Sigstore library","requires_auth":"none","summary":"A single compromised transparency log can bypass multi-log verification thresholds in the sigstore-go library, undermining supply chain integrity guarantees.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sigstore-go","vendor":"sigstore"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/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-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N\u003e1) or WithSignedCertificateTimestamps(N\u003e1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sigstore-go: Multi-log threshold bypass via single compromised log","id":"CVE-2026-49834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Sigstore Timestamp Authority: OOM due to unbounded metric label cardinality","id":"CVE-2026-49835"},"packages":[{"ecosystem":"Go","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/sigstore-go","purl":null,"source":"GHSA-9vcr-p3rj-q5q6"},{"ecosystem":"Go","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/sigstore-go","purl":"pkg:golang/github.com/sigstore/sigstore-go","source":"GHSA-9vcr-p3rj-q5q6"},{"ecosystem":"Go","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/sigstore/sigstore-go","purl":"pkg:golang/github.com/sigstore/sigstore-go","source":"GO-2026-5952"}],"prev":{"headline":"DSpace: Path Traversal possible in LDN message generation","id":"CVE-2026-49833"},"products":["sigstore-go"],"published":"2026-07-17","related":[{"cvss_score":3.1,"headline":"Unbounded loop over untrusted input can lead to endless data attack","id":"CVE-2024-45395","kev_date_added":null,"published":"2024-09-04"}],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-17","vendors":["sigstore"]},"summary":"A single compromised transparency log can bypass multi-log verification thresholds in the sigstore-go library, undermining supply chain integrity guarantees.","url":"https://insights.sbomify.com/CVE-2026-49834/"}