CVE-2007-2232: The CHECK command in Cosign 2.0.1 and earlier allows remote attackers to bypass authentication requirements vi

This month

HIGH 7.5DOWNGRADE

CVE-2007-2232 is a high-severity flaw (CVSS 7.5) affecting cosign. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The CHECK command in Cosign 2.0.1 and earlier allows remote attackers to bypass authentication requirements via CR (\r) sequences in the cosign cookie parameter.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Published	2007-04-25
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: cosign

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2007-04-25 15:19 UTCPublished CVE record published
2026-06-16 22:39 UTCUpdated Record last modified

cosign cosign DOWNGRADE

Affected: 0.7.0 · 0.8.0 · 0.9.0 · 1.0 · 1.1 · 1.5 · 1.6 · 1.7

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.7.0

1. Check installed version

apt-cache policy cosign || rpm -q cosign || cosign --version

2. No fixed release: DOWNGRADE to a release before 0.7.0 (Debian / Ubuntu)

apt-cache madison cosign sudo apt install cosign=<VERSION_BEFORE_0.7.0> sudo apt-mark hold cosign

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cosign sudo dnf downgrade cosign-<VERSION_BEFORE_0.7.0> sudo dnf versionlock add cosign

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Cosign 2.0.1/2.9.4a - CGI Check Cookie Command Remote Authentication Bypass

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2007-2232?

cosign: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2007-2232 being exploited?

CVE-2007-2232 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2007-2232 affect?

CVE-2007-2232 affects cosign. Severity is high (CVSS 7.5). The CHECK command in Cosign 2.0.1 and earlier allows remote attackers to bypass authentication requirements via CR (\r) sequences in the cosign cookie parameter.

How urgent is CVE-2007-2232?

Priority 52/100. High severity; Public exploit reference

Related CVEs

CVE-2026-39395 MEDIUM 4.3 UPGRADE Cosign provides code signing and transparency for containers and binaries
CVE-2024-29903 MEDIUM 4.2 UPGRADE Cosign provides code signing and transparency for containers and binaries
CVE-2024-29902 MEDIUM 4.2 UPGRADE Cosign provides code signing and transparency for containers and binaries
CVE-2023-46737 LOW 3.1 UPGRADE Cosign is a sigstore signing tool for OCI containers
CVE-2022-36056 MEDIUM 5.5 UPGRADE Cosign is a project under the sigstore organization which aims to make signatures invisible infrastructure

References

← Back to latest CVEs