EUVD-2026-100733
GHSA-v888-53v5-qvgj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted Content Credentials input
-
ExploitBypass input validation in C2PA SDK
-
ImpactGain limited unauthorized 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 the target to run an application that uses an affected version of the Content Credentials tooling - Content Credentials Rust SDK (c2pa) ≤ c2pa-v0.90.15, C2PA Tool ≤ c2patool-v0.27.15, or Content Credentials JS SDK ≤ @contentauth/c2pa-web@0.13.4 - and to process attacker-supplied content/manifests through that SDK. Per the CVSS vector (PR:N/UI:N) no authentication or user interaction is needed, and no non-default configuration is called out. The principal limiting factor is impact scope: only 'limited' integrity/write access is gained (I:L, C:N, A:N), so the attacker cannot read data or cause denial of service - the realistic risk is tampering with content-provenance integrity rather than full compromise. |
| Impact | This is a moderate-severity issue (CVSS 5.3) whose signals are mostly consistent but point to limited real-world urgency. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a remotely reachable, low-complexity, unauthenticated flaw requiring no user interaction, which superficially looks serious; however the impact is deliberately scoped to I:L only (C:N/A:N), i.e. 'unauthorized limited write access,' which caps the damage ceiling. No EPSS score was provided in the input, the CVE is NOT on the CISA KEV list, and no public POC is referenced, so exploitation status is: no public exploit identified at time of analysis. No SSVC decision data was supplied. The one notable tension is between the metadata tag 'Authentication Bypass' and the actual CWE-20 (Improper Input Validation) / 'security feature bypass' language in the description - these are related but not identical, so treat the 'Authentication Bypass' framing as approximate and rely on the input-validation characterization. Net: this is a genuine but second-tier priority - patch in normal cycles rather than emergency, prioritized higher where the affected SDKs process untrusted, attacker-supplied content. |
| Exploit ScenarioDerived | An attacker submits maliciously crafted content or a tampered Content Credentials manifest to an application built on the affected C2PA SDK/c2patool, which processes it without user interaction. Improper input validation lets the attacker bypass a security check and obtain limited unauthorized write access to provenance/credential data. No public proof-of-concept exploit has been 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
Security-control bypass in Adobe's Content Credentials tooling allows remote, unauthenticated attackers to obtain limited unauthorized write access to content handled by affected SDKs by supplying malformed input that the library fails to validate. The issue (CVSS 3.1 score 5.3, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, CWE-20) affects Content Credentials Rust SDK (c2pa) up to c2pa-v0.90.15, C2PA Tool (c2patool) up to v0.27.15, and Content Credentials JS SDK (@contentauth/c2pa-web) up to 0.13.4, and requires only that the target application processes attacker-supplied content or manifests - no authentication, no user interaction, and no non-default configuration are needed. Impact is confined to integrity (I:L) with no confidentiality or availability loss, so the realistic risk is forged or tampered content-provenance records rather than system compromise; no public exploit identified at time of analysis.
RemediationAI
No vendor-published fixed version is enumerated in the available data; the authoritative source is Adobe's advisory APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html), and since the listed affected ranges terminate at c2pa-v0.90.15, c2patool-v0.27.15, and @contentauth/c2pa-web@0.13.4, remediation should move every installed copy of these components to a release beyond those bounds and re-verify with an SBOM scan that covers transitive dependencies as well as direct ones. Until a patched build is deployed, compensating controls should target the sole precondition - ingestion of attacker-supplied input: reject or quarantine C2PA manifests originating outside trusted publishers before they reach the SDK, cross-check incoming provenance assertions against an independently held record of the original publication, and run manifest parsing in a sandboxed, least-privileged process so that the limited write effect cannot reach unrelated data. The trade-offs are reduced functionality for legitimate third-party content ingest, added parsing latency from sandboxing and out-of-band verification, and the operational burden of maintaining a trusted provenance reference; network-level filtering is not a useful control here because the vector is PR:N/UI:N and the attack surface is whatever interface feeds the SDK.
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 root cause class is CWE-20 (Improper Input Validation): attacker-controlled input reaches a security-relevant decision path without adequate validation. In this codebase that path is the parsing and validation of C2PA manifests - CBOR-encoded assertion stores and COSE-based claim/signature structures that Content Credentials uses to record who created, edited, or signed a piece of media. Because the failure is a trust-in-input gap rather than a memory-safety bug, the outcome is a security feature bypass (the reporting PSIRT tagged it 'Authentication Bypass') instead of code execution: content that should fail validation can be accepted, and provenance data that should be rejected can be written, which matches the assessed vector's I:L / C:N / A:N profile. Three separate deliverables are in scope - the Rust core library (c2pa), its command-line driver (c2patool), and the JavaScript binding (@contentauth/c2pa-web) - indicating the defect lives in shared manifest-processing logic used across interfaces, so integrators must update every embedded and transitive copy in their pipeline, not just the one they call directly. Exploitation prerequisites are minimal: the vector PR:N/UI:N confirms no authentication and no victim interaction, and the independent assessment notes no non-default configuration is required; the principal limiter remains scope of impact, since only limited integrity/write access is attainable and no read or denial-of-service effect is possible.
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
Remotely processable crafted input (AV:N/AC:L) with no auth or interaction (PR:N/UI:N) yields only limited write access, so I:L with C:N/A:N 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
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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
Exploit-DB