Content Credentials CVE-2026-48298

The vulnerable code path is triggered when the affected SDK or CLI tool parses a C2PA manifest embedded in a media file - meaning exploitation requires the ability to introduce a crafted C2PA-bearing file into the processing pipeline of the vulnerable component. The CVSS local attack vector (AV:L) indicates the baseline scenario is local file submission to the tool or SDK, but server-side pipelines that accept user-supplied media could expose this to remote, unauthenticated callers depending on deployment architecture (not reflected in the official CVSS). No privileges are required (PR:N) within the tool itself; no user interaction is required (UI:N), meaning no user needs to manually open or approve the file beyond it being passed to the parser. Exploitation is limited by the local-vector classification, the requirement that C2PA manifest processing be active, and the SSVC finding that the vulnerability is not automatable at scale, reducing mass-exploitation viability.

The CVSS base score of 6.2 with vector AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H reflects a local-vector, no-privileges, high-availability-impact scenario - consistent with an attacker supplying a maliciously crafted file to a locally executed tool or SDK pipeline. Real-world priority is low: EPSS at 0.15% (5th percentile) signals minimal exploitation probability, SSVC marks exploitation as 'none' and automatable as 'no', KEV status is absent, and no public proof-of-concept has been identified. The impact is limited strictly to availability (no confidentiality or integrity loss). The AV:L designation limits practical exploitation to scenarios where an attacker can introduce a crafted file into a content processing pipeline - this may be achievable remotely in headless server workflows that consume user-supplied media, but the official vector does not reflect network-reachable exploitation. Defenders in media authentication pipelines should prioritize patching, but this does not represent a critical emergency.

An attacker crafts a C2PA-compliant media file containing a malformed manifest field with a value designed to trigger integer underflow in length or offset arithmetic during parsing. The file is submitted to an application or pipeline using a vulnerable version of the Rust SDK, JS SDK, or c2patool - for example, by uploading it to a content ingestion service or passing it directly to the CLI tool. The parser crashes on the underflowed value, terminating the application and denying service to legitimate users. No public proof-of-concept has been identified at time of analysis.