Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach C2PA SDK/c2patool input surface
-
ExploitSubmit crafted malformed input
-
ExecutionBypass input validation control
-
ImpactGain unauthorized write to content credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation is explicitly gated by 'conditions beyond the attacker's control' (reflected as CVSS AC:H) - the advisory does not name the exact prerequisite, but it implies a required environmental or timing state the attacker cannot force, which is the primary factor limiting reliable exploitation. The attack targets the input-parsing/validation path of applications embedding the C2PA JS SDK (@contentauth/c2pa-web ≤0.13.4), the c2pa Rust SDK (≤0.90.15), or c2patool (≤0.27.15). Per the CVSS vector, no authentication (PR:N) and no user interaction (UI:N) are required, and the vector is network-reachable (AV:N); impact is limited to unauthorized write/integrity (C:N/A:N), i.e., tampering with content credentials rather than data theft or denial of service. Realistic risk is bounded by the high-complexity precondition and by whether a given deployment actually exposes untrusted input to the vulnerable SDK versions. |
| Impact | This is a moderate-priority issue rather than a top-tier emergency. CVSS 3.1 scores it 5.9 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - network-reachable and requiring no privileges or user interaction, but gated by AC:H, which directly reflects the description's statement that 'exploit depends on conditions beyond the attacker's control.' The only impact is to integrity (I:H, unauthorized write access); there is no confidentiality or availability impact. No EPSS score, CISA KEV listing, or POC was provided in the input, so there is no signal of active exploitation or public exploit code. The signals are internally consistent (high complexity dampens an otherwise-attractive unauthenticated network vector), and the lack of exploitation indicators means this is a credibility/integrity-of-provenance concern to patch on a normal cadence, not a drop-everything issue. Note the tag labels this an 'Authentication Bypass' while the CWE (CWE-20 Improper Input Validation) and description frame it as a security-feature bypass yielding write access - a semantic mismatch worth noting but not a contradiction, since the real-world effect is bypassing a protective control. |
| Exploit ScenarioDerived | An attacker crafts malformed input to a system embedding the C2PA SDK or c2patool so that improper input validation lets a protective check be bypassed, allowing the attacker to write or alter content-credential (provenance) data without authorization. Because CVSS AC:H applies and the advisory says success depends on conditions beyond the attacker's control, reliable exploitation requires a specific state or timing to align. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Improper input validation in Adobe's CAI Content Credentials (C2PA) tooling lets a remote, unauthenticated attacker bypass a security check and obtain unauthorized write access to content-credential data, which can be triggered without any user interaction (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, base 5.9). The affected components are the JavaScript SDK @contentauth/c2pa-web through 0.13.4, the Rust c2pa crate through 0.90.15, and c2patool through 0.27.15. Reliability is deliberately constrained: Adobe states exploitation depends on conditions beyond the attacker's control, reflected as high attack complexity, so this is a moderate-priority integrity/tampering issue rather than a top-tier emergency; no public exploit or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS signal was supplied. Impact is limited to integrity (C:N/A:N) - tampering with provenance/credential data rather than data theft or denial of service.
RemediationAI
No vendor-released patch version was identified in the available data at time of analysis; consult Adobe security advisory APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html) for the fixed SDK, crate, and c2patool releases before upgrading. Until patched versions are published and deployed, treat all externally supplied C2PA manifests and media as untrusted input: pre-validate and reject malformed or unexpected manifest structures before handing them to the affected SDK/CLI, and never rely on Content Credentials validation output as an integrity or trust boundary for downstream authorization decisions. Run c2patool and any Rust/JS SDK processing of untrusted files inside a sandboxed or low-privilege container with no write access to shared credential stores, which contains the unauthorized-write impact at the cost of added operational overhead. Where provenance features are not required, disabling C2PA manifest writing/embedding endpoints closes the write path but removes Content Credentials functionality; pinning and monitoring the three component versions in your SBOM with an alert on the fixed releases is recommended given the cross-language scope of the issue.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Content Authenticity Initiative (CAI) Content Credentials stack implements the C2PA (Coalition for Content Provenance and Authenticity) specification, which embeds signed, cryptographically verifiable provenance manifests directly into media assets and validates them on ingest, display, or publication. The vulnerability is rooted in CWE-20 (Improper Input Validation): the manifest parsing/validation path across three separate implementations - the browser/Node JavaScript SDK (@contentauth/c2pa-web ≤ 0.13.4), the Rust c2pa crate (≤ 0.90.15), and the c2patool reference CLI (≤ 0.27.15) - fails to validate attacker-influenced input strictly enough, allowing a security feature (the provenance/trust check itself) to be bypassed and unauthorized writes to content-credential state to occur. Because the flaw is reachable over the network with no privileges (PR:N) and no user interaction (UI:N), the practical exposure depends on whether a given application feeds untrusted media or manifests into these SDK versions; the high complexity (AC:H) reflects an environmental or timing precondition the attacker cannot force, which is the primary factor limiting reliable exploitation. The cross-implementation nature of the advisory indicates a shared validation logic issue, not a single-language defect, so any deployment embedding C2PA validation - web services, desktop tools, or pipeline CLIs - should be inventoried against the affected version ranges.
Know when C2Pa gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Network-reachable input validation flaw needing no auth or interaction (AV:N/PR:N/UI:N); AC:H because exploitation depends on conditions beyond the attacker's control; impact is unauthorized write only, so C:N/I:H/A:N.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
CAI Content Credentials is affected by an Improper Input Validation vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Server-side request forgery in Adobe Content Credentials (CAI Content Credentials SDK) allows unauthenticated remote att
Server-Side Request Forgery in Adobe's C2PA (Content Credentials) SDK family - the Rust SDK (c2pa), the Node.js web SDK
Denial of service in Adobe's CAI (Content Authenticity Initiative) Content Credentials SDK stems from uncontrolled resou
Uncontrolled resource consumption in the Adobe CAI Content Credentials SDK lets unauthenticated, remote attackers exhaus
Improper input validation in the Adobe CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass a
Improper input validation in the CAI Content Credentials SDK (Adobe security bulletin APSB26-163) lets unauthenticated r
Unauthenticated remote attackers can bypass a security feature in Adobe's CAI Content Credentials SDK and gain unauthori
Improper input validation in the CAI Content Credentials SDK allows a remote, unauthenticated attacker to feed crafted i
Integer overflow (CWE-190) in the CAI Content Credentials SDK lets unauthenticated remote attackers crash applications t
Denial-of-service in the CAI Content Credentials SDK allows remote unauthenticated attackers to exhaust system resources
Denial of service in the CAI Content Credentials SDK allows remote, unauthenticated attackers to exhaust system resource
Application denial-of-service in the Adobe CAI Content Credentials SDK lets unauthenticated remote attackers exhaust sys
EUVD-2026-100717
GHSA-8mr3-g9cx-29pj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB