Content Credentials SDK CVE-2026-48377

Exploitation requires that an application or workflow ingests and processes attacker-controlled input through an affected component - c2patool (≤0.27.15), the c2pa Rust SDK (≤0.90.15), or the @contentauth/c2pa-web JS SDK (≤0.13.4) - such as verifying or reading a Content Credentials manifest/asset supplied by an untrusted party. Per CVSS PR:N/UI:N, no authentication or user interaction is needed, which removes the main limiting factors. The principal limits on real-world risk are therefore scope and impact rather than access: only applications that actually embed a vulnerable version and feed it untrusted content are exposed, and the resulting capability is confined to limited unauthorized write (integrity) with no data disclosure or denial of service.

This is a genuine but modest-severity issue, not a top-tier emergency. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N = 5.3 Medium) describes a remotely reachable, low-complexity, unauthenticated flaw with no user interaction, which on paper is attractive to attackers. However, impact is deliberately narrow: integrity only (I:L - 'limited write access'), with no confidentiality (C:N) and no availability (A:N) effect, and no scope change (S:U). No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active or imminent exploitation; per the precision rules this is 'no public exploit identified at time of analysis.' The signals are therefore consistent rather than conflicting - a network-reachable, unauthenticated input-validation bug whose real-world damage ceiling is low. Note one framing caveat: the affected assets are developer SDKs/libraries and a CLI (c2patool, c2pa Rust SDK, @contentauth/c2pa-web), so 'network vector' realistically means these components process attacker-supplied Content Credentials data embedded in media/manifests rather than exposing a listening service - defenders should interpret AV:N as data-borne exposure. SSVC inputs (exploitation, automatable, technical impact) were not provided and cannot be assessed.

An attacker crafts a malicious Content Credentials manifest or input that exploits improper input validation (CWE-20) in the c2pa SDK/c2patool when an application ingests or verifies it, bypassing an intended security check without authentication or user interaction. This yields limited unauthorized write access, for example tampering with or spoofing provenance/credential state that the application trusts. No public exploit code is identified at time of analysis, and the low attack complexity means a reliable crafted input could be reused across applications embedding the affected libraries.