Quick answers
- Is CVE-2026-100120 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100120 being exploited in the wild.
- How severe is CVE-2026-100120?
- High severity, with a CVSS score of 7.5, published 13 October 2026.
- Which products and versions are affected?
- Adobe C2PA Tool (c2patool) c2patool-v0.27.15 and earlier; Adobe Content Credentials JS SDK @contentauth/c2pa-web@0.13.4 and earlier; Adobe Content Credentials Rust SDK (c2pa) c2pa-v0.90.15 and earlier.
- Is there a fix for CVE-2026-100120?
- Yes: fixed in Content Credentials Rust SDK c2pa-v0.91.1; C2PA Tool c2patool-v0.28.1; Content Credentials JS SDK @contentauth/c2pa-web@0.15.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100120 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100120?
- Check whether you run Adobe C2pa, Adobe C2PA Tool (c2patool), Adobe C2pa-Web or one of the others listed 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.
How to fix
- Fixed in: Content Credentials Rust SDK c2pa-v0.91.1; C2PA Tool c2patool-v0.28.1; Content Credentials JS SDK @contentauth/c2pa-web@0.15.3
Technical details
The advisory covers multiple vulnerability classes (improper input validation, certificate validation, SSRF, access control, resource consumption) in the Content Credentials Rust SDK, C2PA Tool, and Content Credentials JS SDK. All vulnerabilities are network-accessible with no privileges or user interaction required. Exploits would allow attackers to bypass cryptographic verification, forge credentials, or cause denial-of-service.
Affected products
- Adobe Content Credentials Rust SDK (c2pa) c2pa-v0.90.15 and earlier
- Adobe C2PA Tool (c2patool) c2patool-v0.27.15 and earlier
- Adobe Content Credentials JS SDK @contentauth/c2pa-web@0.13.4 and earlier
Timeline
- 2026-10-13: disclosed