How severe is CVE-2026-22703?

CVE-2026-22703 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-22703 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-22703?

CVE-2026-22703 affects Sigstore Cosign. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-22703?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-22703 have an EU (EUVD) identifier?

Yes. CVE-2026-22703 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-1868.

When was CVE-2026-22703 published?

CVE-2026-22703 was published on 2026-01-10 and last updated on 2026-06-17.

CVE-2026-22703

CVE-2026-22703 is a medium-severity vulnerability in Sigstore Cosign with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-1868
Weakness: CWE-345
Affected product: Sigstore Cosign
Published: 2026-01-10
Last modified: 2026-06-17

Description

Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.

Frequently asked questions

What is CVE-2026-22703?: Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.
How severe is CVE-2026-22703?: CVE-2026-22703 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-22703 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-22703?: CVE-2026-22703 affects Sigstore Cosign. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-22703?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-22703 have an EU (EUVD) identifier?: Yes. CVE-2026-22703 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-1868.
When was CVE-2026-22703 published?: CVE-2026-22703 was published on 2026-01-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:sigstore:cosign:*:*:*:*:*:*:*:*

More vulnerabilities in Sigstore Cosign

CVE-2022-35929 — High (CVSS 7.1): cosign is a container signing and verification utility. In versions prior to 1.10.1 cosign can report a false positive…
CVE-2022-36056 — Medium (CVSS 5.5): Cosign is a project under the sigstore organization which aims to make signatures invisible infrastructure. In versions…
CVE-2026-39395 — Medium (CVSS 4.3): Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, cosign…
CVE-2024-29903 — Medium (CVSS 4.2): Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted…
CVE-2024-29902 — Medium (CVSS 4.2): Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, a remote image with…
CVE-2026-24122 — Low (CVSS 3.7): Cosign provides code signing and transparency for containers and binaries. In versions 3.0.4 and below, an issuing…

All CVEs affecting Sigstore Cosign →

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
CVE-2026-50214 — Critical (CVSS 9.8): The /v1/Plan service relies entirely on a shared global API token for full administrative management, allowing…
CVE-2025-15385 — Critical (CVSS 9.8): Insufficient Verification of Data Authenticity vulnerability in TECNO Mobile com.Afmobi.Boomplayer allows…

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →