Skip to main content
VulnerabilityPublished

CVE-2026-102884: sse-secure-systems connaisseur · Incorrect Comparison

Affects sse-secure-systems connaisseurSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.11.1 when convenient.

Data as of 19 Nov 2026, 20:51 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.3
Patch
Available – fixed in 3.11.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade connaisseur and sse-secure-systems/connaisseur to 3.11.1.

Affected software

ProductAffectedFixed in
sse-secure-systemsconnaisseurAffected
  • <3.11.1
Fixed in
  • 3.11.1
GitHubsse-secure-systems/connaisseurpkg:github/sse-secure-systems/connaisseurOther threatsAffected
  • <3.11.1
Fixed in
  • 3.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Connaisseur to version 3.11.1 or later, where this issue is fixed. No other mitigation is necessary as the fix addresses the root cause of the incorrect signature counting. Policies using a single trust root or the required option are not affected by this vulnerability.

Description

CVE-2026-102884 is a vulnerability in sse-secure-systems' Connaisseur admission controller for Kubernetes. Before version 3.11.1, the Cosign validator incorrectly counted valid signature layers instead of distinct trust roots when using trustRoot: "*" policies with explicit thresholds or implicit require-all policies. This flaw allows an attacker controlling one trust root's signing key to bypass the intended signer quorum by attaching multiple signatures, causing unintended admission. Policies with a single trust root or using the required option are not affected. The issue is fixed in version 3.11.1.

References

Community reviews

Loading reviews…