Quick answers
- Is CVE-2026-48290 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48290 being exploited in the wild.
- How severe is CVE-2026-48290?
- High severity, with a CVSS score of 8.2, published 14 July 2026.
- Which products and versions are affected?
- Adobe Content Credentials Command-Line Tool <= c2patool-v0.16.5; Adobe Content Credentials JS SDK <= @contentauth/c2pa-v0.16.0; Adobe Content Credentials Rust SDK <= c2pa-v0.84.0.
- Is there a fix for CVE-2026-48290?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-48290 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-48290?
- Check whether you run Adobe Content Credentials Command-Line Tool, Adobe Content Credentials JS SDK or Adobe Content Credentials Rust SDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability (CWE-918) exists in the Adobe Content Authenticity (CAI) SDKs and command-line tools. The flaw allows an attacker to bypass security boundaries and potentially achieve arbitrary code execution or script injection by manipulating how the application handles external requests. Exploitation requires a local user to interact with a maliciously crafted URL or a compromised web page. The vulnerability affects the Rust SDK, JavaScript SDK, and the C2PA command-line tool, with patches available in newer versions (e.g., Rust SDK v0.85.2).
Affected products
- Adobe Content Credentials Rust SDK <= c2pa-v0.84.0
- Adobe Content Credentials Command-Line Tool <= c2patool-v0.16.5
- Adobe Content Credentials JS SDK <= @contentauth/c2pa-v0.16.0
Timeline
- 2026-07-14: disclosed
- 2026-07-14: advisory