Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSupply crafted content to SDK-backed application
-
ExploitTrigger improper input validation (CWE-20)
-
ExecutionBypass content-credential security check
-
ImpactGain unauthorized limited write access
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 requires an application or pipeline that ingests attacker-supplied content/manifests through a vulnerable version of the Content Credentials components (c2pa-rs ≤ v0.90.15, c2patool ≤ v0.27.15, or @contentauth/c2pa-web ≤ 0.13.4); the vulnerable input-validation path is the C2PA content/manifest parsing-and-verification logic. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication and no user interaction are needed against default use. The principal LIMITING factors are: exposure exists only where untrusted content is actually processed by the SDK/tool, and impact is bounded to limited-integrity write access (I:L) with no data disclosure (C:N) and no availability loss (A:N), so a successful attack tampers with provenance/write state rather than fully compromising the host. |
| Impact | This is a MEDIUM-severity issue (CVSS 5.3) that signals support treating as a moderate, not top-tier, priority. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N shows a genuinely favorable attack profile for an adversary - network-reachable, low complexity, no privileges, no user interaction - but the impact is deliberately narrow: integrity-only and LOW (I:L), with zero confidentiality (C:N) and zero availability (A:N) effect. The 'unauthorized limited write access' in the description is consistent with that I:L rating, so the easy-to-reach but low-consequence nature is what caps the score at medium. No EPSS probability was provided in the input, so exploitation likelihood cannot be quantified. There is no CISA KEV listing and no public exploit referenced, so exploitation status is: no public exploit identified at time of analysis. No SSVC decision data (exploitation/automatable/technical-impact) was supplied. Signals are therefore consistent rather than conflicting - an easily reachable but low-impact bypass - but several key risk inputs (EPSS, SSVC, POC status) are simply MISSING from the data and should be checked before final prioritization. |
| Exploit ScenarioDerived | An attacker submits crafted content or a manipulated C2PA manifest to an application that processes it through the vulnerable Content Credentials SDK/tool. Because input validation is incomplete, the attacker bypasses a content-credential security check and obtains limited unauthorized write access without any user interaction. No public exploit code is identified at time of analysis. |
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 tooling (the Rust SDK c2pa-rs, the c2patool CLI, and the @contentauth/c2pa-web JS SDK) lets remote, unauthenticated attackers who supply crafted content manifests bypass a security feature and obtain limited unauthorized write access to content-provenance state. Per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N vector, no credentials or user interaction are required, but the impact is bounded to low-integrity writes with no confidentiality or availability loss, giving this a MEDIUM severity of 5.3. There is no public exploit identified at time of analysis and no KEV listing; the practical exposure is limited to applications and pipelines that actually ingest untrusted content or manifests into the affected component versions.
RemediationAI
The primary fix is to upgrade off the vulnerable Content Credentials components - c2pa-rs above v0.90.15, c2patool above v0.27.15, and @contentauth/c2pa-web above v0.13.4 - using the exact patched releases listed in Adobe security bulletin APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html); the provided data does not specify the exact fixed version numbers, so confirm them against that advisory rather than assuming a patch level. Where immediate upgrade is not possible, the most effective compensating control is to stop feeding untrusted content into the vulnerable parser: quarantine external media and manifests and only validate them in an isolated, non-privileged process or throwaway container that has no write access to your signing keys, provenance store, or production storage - the trade-off is added latency and operational complexity for every verification. For the JS SDK, restrict which endpoints or browser contexts may process third-party C2PA manifests, since the attack surface is any auto-ingesting upload or verification endpoint reachable by an unauthenticated client. Note that signature validation performed downstream of the vulnerable parsing step will not help, because the bypass occurs inside that parsing/validation path itself. Finally, monitor provenance/signing services for unexpected write operations, as the assessed impact is limited unauthorized writes (I:L) rather than data theft or denial of service.
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
CVE-2026-102501 is rooted in CWE-20 (Improper Input Validation) within Adobe's Content Authenticity Initiative (CAI) Content Credentials implementation, which implements the C2PA provenance standard. The affected components are the parsing-and-verification path used to ingest C2PA manifests: the Rust library c2pa-rs (c2pa-v0.90.15 and earlier), the c2patool CLI (c2patool-v0.27.15 and earlier), and the JavaScript web SDK @contentauth/c2pa-web (0.13.4 and earlier). Because the defect is a validation failure rather than a memory-safety or authentication flaw, the consequence is a security-feature bypass: crafted input is accepted by the manifest/claim validation logic and the SDK then performs limited write operations (signing/provenance state, I:L) on attacker-influenced data instead of rejecting it. The network attack vector with low complexity and no privileges or UI interaction (AV:N/AC:L/PR:N/UI:N) means any service that automatically processes attacker-supplied media or manifests - an upload pipeline, a signing service, a verification API - can be triggered without social engineering. Impact stops at integrity: no data disclosure (C:N) and no availability loss (A:N) are assessed, so the realistic harm is falsified or tampered provenance metadata rather than host compromise. The Adobe PSIRT tagging of this issue as an authentication/security-feature bypass is consistent with that reading.
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:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Remote unauthenticated processing of untrusted content (AV:N/AC:L/PR:N/UI:N); only limited unauthorized write yields I:L, with no confidentiality or availability impact and unchanged scope.
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 limited write access. 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-100745
GHSA-cg8f-77jv-6647
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB