{"answers":{"affected":"2 open source packages ship an affected version, including dev.sigstore:sigstore-java.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48791 exists.","fix":"Upgrade dev.sigstore:sigstore-java to 2.1.0 or later.","what":"CVE-2026-48791 is a low-severity vulnerability in sigstore-java, published on 12 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48791 and fix it if it is affected.\n\nWhat it is: CVE-2026-48791 is a low-severity vulnerability in sigstore-java, published on 12 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48791 exists.\n\nAffected packages and fixed versions:\n- dev.sigstore:sigstore-java (Maven): affected from 2.0.0; fixed in 2.1.0\n- dev.sigstore:sigstore-java (Maven): affected from 2.0.0; fixed in 2.1.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-48791/ (Markdown: https://insights.sbomify.com/CVE-2026-48791/index.md)","id":"CVE-2026-48791","markdown":"https://insights.sbomify.com/CVE-2026-48791/index.md","name":"CVE-2026-48791","record":{"aliases":["GHSA-qqw8-7c2r-jxch","UBUNTU-CVE-2026-48791"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java signing library","requires_auth":"high_privilege","summary":"Attackers can bypass signature verification by reusing old certificates if the integrated time check is skipped, allowing unauthorized artifact trust.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"sigstore-java is a sigstore java client for interacting with sigstore infrastructure. Version 2.0.0 erroneously removed verification of the integrated (Rekor entry) time) against the Fulcio certificate. Version 2.1.0 re-added this verification with enhancements that adhere to the Sigstore verification spec. The old sigstore-conformance test for this check was built incorrectly. This vulnerability impacts only users verifying bundles with `dev.sigstore:sigstore-java:2.0.0`. Older versions are not affected; it is fixed in `dev.sigstore:sigstore-java:2.1.0` A malicious actor may exploit this if they were able to access a users system and exfiltrate the temporary private key used during signing and then reuse an old fulcio certificate later without requiring direct access to the user's credentials. Users may protect themselves by re-verifying their artifacts using the newest sigstore-java or another current sigstore client. Transparency logs may also be audited for unauthorized signatures for a suspected reused identity.","ecosystems":["Maven"],"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 Java has a vulnerability with bundle verification of integratedTime","id":"CVE-2026-48791","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Security feature bypass in pam usb","id":"CVE-2026-48792"},"packages":[{"ecosystem":"Maven","fixed":["2.1.0"],"introduced":["2.0.0"],"last_affected":[],"package":"dev.sigstore:sigstore-java","purl":null,"source":"GHSA-qqw8-7c2r-jxch"},{"ecosystem":"Maven","fixed":["2.1.0"],"introduced":["2.0.0"],"last_affected":[],"package":"dev.sigstore:sigstore-java","purl":"pkg:maven/dev.sigstore/sigstore-java","source":"GHSA-qqw8-7c2r-jxch"}],"prev":{"headline":"turso-cli persists Turso platform JWT with world-readable (0o644) file permissions","id":"CVE-2026-48790"},"products":["sigstore-java"],"published":"2026-08-12","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-08-13","vendors":["sigstore"]},"summary":"Attackers can bypass signature verification by reusing old certificates if the integrated time check is skipped, allowing unauthorized artifact trust.","url":"https://insights.sbomify.com/CVE-2026-48791/"}