When the `signatureFormat: bundle` Fix Runs Into a policy-controller Key Policy
policy-controller v0.15.1: a public-key policy rejected an image signed in cosign v3.1.3's default format ("no signatures found"); with signatureFormat: bundle, "the authority must be keyless". When It Runs โ Run Repor
policy-controller v0.15.1: a public-key policy rejected an image signed in cosign v3.1.3's default format ("no signatures found"); with signatureFormat: bundle, "the authority must be keyless".
When It Runs โ Run Report #RR16 ยท Testing what infrastructure actually does.
Provider ยท Component: Sigstore policy-controller (with cosign) ยท whether a
ClusterImagePolicywith a public-key authority admits an image signed by cosign v3 in its default format โ with the policy as is, with the commonly shared fixsignatureFormat: bundle, and with that fix plus an attestation check
Versions tested: measured โ policy-controller v0.15.1 and cosign v3.1.3 (the latest releases of each as of 2026-09-28; cosign v3.1.4, released on 2026-10-20, was not measured), one version each. source-read โpkg/webhook/validator.goandpkg/apis/policy/v1alpha1/clusterimagepolicy_types.goat policy-controller v0.15.1, andcmd/cosign/cli/options/sign.go,cmd/cosign/cli/sign/sign.goandcmd/cosign/cli/signcommon/common.goat cosign v3.1.3. The reports quoted below name cosign v3.0.2 and v3.0.4 and policy-controller 0.13.1 and v0.15.1 โ not measured.
Config profile: a single-nodekindcluster (kind v0.33.0, nodekindest/node:v1.34.11, digest-pinned) on a dedicated test VM without internet access; policy-controller from the official Helm chart 0.10.8 with the image set to v0.15.1 by digest and TUF disabled (offline); a local registry; a key pair made for the lab; one test image signed twice with the key and without a transparency log โ in cosign v3.1.3's default format and in the older format (--new-bundle-format=false); three policies on the same key authority, applied one at a time โ A as is (nosignatureFormat), B withsignatureFormat: bundle, C with B plus the attestation check from issue #1899; each admission tried withkubectl run.
Verified on: 2026-11-16 (desk sources re-checked; policy-controller v0.15.1 and cosign v3.1.4 were the latest releases) ยท lab measured 2026-09-29.
Affects: policy-controller v0.15.1ClusterImagePolicyauthorities that use a public key, for images signed by cosign v3.1.3 in its default format: with the policy as is, the image was rejected with "no signatures found"; withsignatureFormat: bundleset on the authority, it was still rejected, with "when using the new bundle format, the authority must be keyless".
TL;DR: On policy-controller v0.15.1, a public-keyClusterImagePolicyrejected an image that cosign v3.1.3 had signed in its default format ("no signatures found"), and the fix commonly shared for cosign v3 signatures โsignatureFormat: bundleon the authority โ still rejected it, with the error "when using the new bundle format, the authority must be keyless"; the same image signed in cosign's older format was admitted by the unchanged policy.
Full report: https://whenitruns.substack.com/p/when-the-signatureformat-bundle-fix
Reproduction repo: https://github.com/whenitruns/when-the-signatureformat-bundle-fix-runs-into-a-policy-controller-key-policy
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes โ full credit and traffic to the original publisher.