CVE-2026-22703: CWE-345: Insufficient Verification of Data Authenticity in sigstore cosign
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.
AI Analysis
Technical Summary
Cosign is a tool within the sigstore project that provides cryptographic signing and transparency for container images and binaries, leveraging a transparency log called Rekor. The vulnerability identified as CVE-2026-22703 (CWE-345) arises from insufficient verification of the authenticity of data embedded in cosign bundles prior to versions 2.6.2 and 3.0.4. Specifically, when cosign verifies a Rekor entry during artifact signature validation, it checks the Rekor entry's signature but fails to adequately confirm that the Rekor entry references the artifact's digest, the signature, or the user's public key. This flaw allows an attacker who has compromised a user's signing key or identity to craft a cosign bundle containing arbitrary Rekor entries unrelated to the actual artifact. As a result, cosign would accept these bundles as valid, effectively allowing the attacker to bypass audit mechanisms that rely on transparency logs to verify the provenance and integrity of signed artifacts. The vulnerability impacts the integrity of the signing process but does not affect confidentiality or availability. Exploitation requires local privileges (AV:L) and low complexity (AC:L), with privileges at the level of a user with signing key access (PR:L), and no user interaction (UI:N) is needed. The scope remains unchanged (S:U). The CVSS v3.1 base score is 5.5, reflecting a medium severity. This vulnerability is particularly critical in environments where cosign is used to secure supply chains and enforce trust in containerized deployments. The issue has been addressed by patches in cosign versions 2.6.2 and 3.0.4, which implement stricter verification ensuring that the Rekor entry corresponds exactly to the artifact's digest, signature, and public key. Organizations using affected versions should upgrade immediately to prevent potential integrity compromises.
Potential Impact
For European organizations, this vulnerability poses a risk to the integrity of software supply chains that utilize cosign for signing container images and binaries. Attackers who gain access to signing keys can create fraudulent signatures that appear valid, undermining trust in deployed software and potentially allowing malicious code to be distributed undetected. This can lead to compromised systems, data breaches, or disruption of services if malicious containers or binaries are deployed in production environments. The impact is particularly significant for sectors relying heavily on containerization and DevSecOps practices, such as financial services, telecommunications, and critical infrastructure. Although confidentiality and availability are not directly affected, the loss of integrity can have cascading effects on compliance with regulations like the EU Cybersecurity Act and NIS2 Directive, which emphasize supply chain security. The inability to audit signing events accurately also weakens incident response and forensic capabilities. Organizations with large-scale container deployments or those participating in open-source software supply chains are at higher risk.
Mitigation Recommendations
The primary mitigation is to upgrade cosign to version 2.6.2 or 3.0.4 or later, where the vulnerability has been patched with enhanced verification of Rekor entries against artifact digests, signatures, and public keys. Organizations should enforce strict access controls and monitoring around signing keys to prevent compromise, including hardware security modules (HSMs) or secure key vaults. Implement multi-factor authentication and regular key rotation policies for signing credentials. Additionally, integrate continuous monitoring and alerting on signing activities and transparency log anomalies to detect suspicious behavior promptly. Conduct regular audits of the software supply chain and signing processes to ensure compliance with security policies. For critical deployments, consider implementing out-of-band verification of signed artifacts and transparency logs. Finally, educate developers and DevOps teams about the importance of using updated tooling and secure key management practices to prevent exploitation.
Affected Countries
Germany, France, Netherlands, United Kingdom, Sweden, Finland
CVE-2026-22703: CWE-345: Insufficient Verification of Data Authenticity in sigstore cosign
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.
AI-Powered Analysis
Technical Analysis
Cosign is a tool within the sigstore project that provides cryptographic signing and transparency for container images and binaries, leveraging a transparency log called Rekor. The vulnerability identified as CVE-2026-22703 (CWE-345) arises from insufficient verification of the authenticity of data embedded in cosign bundles prior to versions 2.6.2 and 3.0.4. Specifically, when cosign verifies a Rekor entry during artifact signature validation, it checks the Rekor entry's signature but fails to adequately confirm that the Rekor entry references the artifact's digest, the signature, or the user's public key. This flaw allows an attacker who has compromised a user's signing key or identity to craft a cosign bundle containing arbitrary Rekor entries unrelated to the actual artifact. As a result, cosign would accept these bundles as valid, effectively allowing the attacker to bypass audit mechanisms that rely on transparency logs to verify the provenance and integrity of signed artifacts. The vulnerability impacts the integrity of the signing process but does not affect confidentiality or availability. Exploitation requires local privileges (AV:L) and low complexity (AC:L), with privileges at the level of a user with signing key access (PR:L), and no user interaction (UI:N) is needed. The scope remains unchanged (S:U). The CVSS v3.1 base score is 5.5, reflecting a medium severity. This vulnerability is particularly critical in environments where cosign is used to secure supply chains and enforce trust in containerized deployments. The issue has been addressed by patches in cosign versions 2.6.2 and 3.0.4, which implement stricter verification ensuring that the Rekor entry corresponds exactly to the artifact's digest, signature, and public key. Organizations using affected versions should upgrade immediately to prevent potential integrity compromises.
Potential Impact
For European organizations, this vulnerability poses a risk to the integrity of software supply chains that utilize cosign for signing container images and binaries. Attackers who gain access to signing keys can create fraudulent signatures that appear valid, undermining trust in deployed software and potentially allowing malicious code to be distributed undetected. This can lead to compromised systems, data breaches, or disruption of services if malicious containers or binaries are deployed in production environments. The impact is particularly significant for sectors relying heavily on containerization and DevSecOps practices, such as financial services, telecommunications, and critical infrastructure. Although confidentiality and availability are not directly affected, the loss of integrity can have cascading effects on compliance with regulations like the EU Cybersecurity Act and NIS2 Directive, which emphasize supply chain security. The inability to audit signing events accurately also weakens incident response and forensic capabilities. Organizations with large-scale container deployments or those participating in open-source software supply chains are at higher risk.
Mitigation Recommendations
The primary mitigation is to upgrade cosign to version 2.6.2 or 3.0.4 or later, where the vulnerability has been patched with enhanced verification of Rekor entries against artifact digests, signatures, and public keys. Organizations should enforce strict access controls and monitoring around signing keys to prevent compromise, including hardware security modules (HSMs) or secure key vaults. Implement multi-factor authentication and regular key rotation policies for signing credentials. Additionally, integrate continuous monitoring and alerting on signing activities and transparency log anomalies to detect suspicious behavior promptly. Conduct regular audits of the software supply chain and signing processes to ensure compliance with security policies. For critical deployments, consider implementing out-of-band verification of signed artifacts and transparency logs. Finally, educate developers and DevOps teams about the importance of using updated tooling and secure key management practices to prevent exploitation.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-08T19:23:09.857Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6961f0b8c540fa4b5432b9fc
Added to database: 1/10/2026, 6:24:56 AM
Last enriched: 1/10/2026, 6:39:34 AM
Last updated: 1/10/2026, 9:14:39 PM
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0824: Cross Site Scripting in questdb ui
MediumCVE-2025-13393: CWE-918 Server-Side Request Forgery (SSRF) in marceljm Featured Image from URL (FIFU)
MediumCVE-2025-12379: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in averta Shortcodes and extra features for Phlox theme
MediumCVE-2026-0822: Heap-based Buffer Overflow in quickjs-ng quickjs
MediumCVE-2026-0821: Heap-based Buffer Overflow in quickjs-ng quickjs
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.