Skip to main content
Menu
CVEs

Connaisseur multi-signature threshold bypass in Cosign verification

CVE-2026-102884Published November 19, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.11.1
Who is exposed
Not reported

Summary

Connaisseur, a Kubernetes admission controller that verifies container image signatures, counts repeated signatures from one trust root as separate approvals when a multi-signature policy uses a wildcard trust root with a threshold or require-all rule. An attacker who holds the signing key for one configured trust root, and can attach several signatures to an image, can reach this over the network after logging in with low privileges, and get the image admitted without the intended group of independent signers.

Written by a model

Original description

Connaisseur is an admission controller that integrates container image signature verification into a Kubernetes cluster. Prior to 3.11.1, the Cosign validator counts valid signature layers rather than distinct trust roots for trustRoot: "*" policies using an explicit threshold or an implicit require-all policy. An attacker who controls one configured trust root's signing key and can attach multiple signatures to an image can satisfy a threshold intended to require multiple independent roots, causing admission without the intended signer quorum. Policies using a single trust root or the required option are not affected. This issue is fixed in 3.11.1.

What to do

Upgrade to a fixed version: 3.11.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-102884 (Connaisseur: Cosign multi-signature threshold bypass through repeated signatures from one trust root), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-102884 (entry last updated 2026-11-19):
Affected:
- sse-secure-systems connaisseur: fixed in 3.11.1
Fixed versions: 3.11.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-102884 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102884 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sse-secure-systems/connaisseur/security/advisories/GHSA-69hh-55g9-hx9g
- https://github.com/sse-secure-systems/connaisseur/pull/2150
- https://github.com/sse-secure-systems/connaisseur/commit/1410707c2a3ed369ab1d354a6e3f493a1c32bc4c
- https://github.com/sse-secure-systems/connaisseur/releases/tag/v3.11.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-102884
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-102884"}.

Affected versions

cve.now Index

9Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-102884

Is CVE-2026-102884 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-102884?

connaisseur: before 3.11.1.

Source: cve.now feed data

How do I fix CVE-2026-102884?

Upgrade to a fixed version: 3.11.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.