CAI Content Credentials CVE-2026-102502

Exploitation targets the signature-verification path of the CAI Content Credentials implementations - the c2patool CLI (≤0.27.15), the Rust c2pa SDK (≤0.90.15), and the @contentauth/c2pa-web JS SDK (≤0.13.4) - specifically when these components verify a C2PA manifest's cryptographic signature on attacker-supplied content. Per the CVSS vector (PR:N/UI:N/AC:L) no authentication, no user interaction, and no special configuration are stated as required, so default verification workflows that ingest untrusted assets are exposed. The limiting factors are the scope of impact rather than preconditions: the flaw yields only 'limited write access' / partial integrity (I:L) with no confidentiality or availability impact, and exploitation is only meaningful where the application relies on Content Credentials verification results as a security/trust decision.

This is a moderate-severity integrity issue, not an urgent priority. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3) indicates a network-reachable, low-complexity, unauthenticated flaw requiring no user interaction, but with impact limited to partial integrity (I:L) and zero confidentiality or availability impact - consistent with the description's 'unauthorized limited write access' via a signature-verification bypass (CWE-347). No EPSS score was provided, the CVE is not listed in CISA KEV, and no public proof-of-concept is referenced, so there is no evidence of active or imminent exploitation - the risk is theoretical at time of analysis. The signal set is internally consistent: a security-feature-bypass with low integrity impact matches a cryptographic verification weakness that lets an attacker forge/alter provenance assertions rather than achieve code execution or data theft. One caveat: the 'Jwt Attack' tag is questionable because Content Credentials (C2PA) relies on COSE/CBOR signatures rather than JWT, so the JWT framing may be a mislabel - verify the exact signature format against the Adobe advisory before building detections around JWT.

An attacker crafts a media asset or manifest whose cryptographic signature is malformed or forged such that the vulnerable Content Credentials verifier accepts it as valid, allowing the attacker to present tampered content provenance as authentic. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, this can be attempted remotely and unauthenticated with no victim interaction, though impact is confined to limited integrity (I:L) - no code execution or data disclosure. No public exploit code is identified at time of analysis.