Content Credentials SDK CVE-2026-48444

Exploitation requires that the attacker can deliver a crafted C2PA asset file to an application using the affected Rust SDK (≤ c2pa-v0.90.5), JS SDK (≤ @contentauth/c2pa-web@0.12.0), or c2patool CLI (≤ c2patool-v0.27.5) for processing. The local attack vector (AV:L) in the CVSS vector indicates the exploitable path is file or data ingestion rather than a directly reachable network port - for example, a file upload endpoint, a media processing queue, or direct CLI invocation with a malicious argument. No authentication (PR:N) and no user interaction (UI:N) are required once the crafted input reaches the parsing code. Exploitation is limited to deployments that process attacker-controlled C2PA content; applications consuming only internally generated or fully trusted assets face no practical risk. There is no indication from available data that a non-default configuration flag is required to trigger the vulnerable code path.

The CVSS base score of 6.2 (Medium) reflects AV:L - exploitation requires supplying a crafted asset to the application's processing pipeline rather than directly attacking a network listener, which substantially limits the realistic attacker population. Complexity is low (AC:L), no privileges are required (PR:N), and no user interaction is needed (UI:N), meaning once a malicious file enters the processing path the crash is reliable and unaided. Impact is availability-only (A:H, C:N, I:N), confirming this is a crash-level denial-of-service with no data exfiltration or code execution capability indicated. No EPSS data was provided in the intelligence package, leaving exploitation probability unquantified, and the vulnerability is absent from the CISA KEV catalog. Practically, services that ingest untrusted, externally submitted C2PA-signed media - image authenticity verification pipelines, digital journalism tooling, media asset management - carry non-trivial risk; even a mid-sized municipal IT team in gniezno operating a public content-verification portal should treat this as a patching priority given the low complexity and zero-interaction requirement once input reaches the parser. Applications processing only internally generated or trusted C2PA content face negligible risk.

An attacker submits a specially crafted C2PA-formatted asset file - for example, a manipulated JPEG or MP4 with a malformed manifest containing integer values engineered to overflow - to any service that invokes the affected SDK for content-authenticity verification. The parser arithmetic wraps around, producing an invalid memory operation that crashes the application process, rendering the verification service unavailable. No public proof-of-concept code has been identified at time of analysis.