EUVD-2026-100721
GHSA-fpx2-8c59-66m6
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK input interface over network
-
DeliverySubmit crafted malformed content/credential data
-
ExploitBypass improper input validation check
-
ExecutionGain unauthorized write to credential data
-
ImpactForge or tamper content provenance
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | The target application must embed or expose the CAI Content Credentials SDK's input-processing path in a network-reachable manner; exploitation then requires supplying crafted input that the SDK fails to validate properly, bypassing its integrity/security checks to gain unauthorized write access. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, no special privileges, and no user interaction are required against affected SDK versions. The principal limiting factor is exposure: the SDK is a specialized provenance component, so real risk depends on whether an application actually accepts untrusted input through the vulnerable code path, and impact is confined to integrity (forged/tampered Content Credentials) with no direct confidentiality or availability loss. |
| Impact | This is a medium-to-high severity integrity flaw (CVSS 7.5, I:H only) in the CAI Content Credentials SDK, assessed as improper input validation (CWE-20) leading to a security-feature bypass and unauthorized write access. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated path with no user interaction, which on paper makes it attractive to attackers; however, the real-world signal set is thin. There is NO EPSS score, NO CISA KEV listing, and NO public exploit provided in the input, so exploitation is currently theoretical rather than demonstrated - the status is 'no public exploit identified at time of analysis.' The impact is bounded: confidentiality and availability are explicitly N, so this is purely an integrity/trust-model bypass (the SDK's job is to assert content provenance/authenticity, so 'unauthorized write access' most plausibly means forging or tampering with Content Credentials rather than full RCE). Signal conflict to note: the input Tag says 'Authentication Bypass' while the description and CWE describe a 'security feature bypass' via input validation - these are not identical, and the CVSS shows no privilege requirement, so treat 'authentication bypass' loosely. Net: a credible integrity issue warranting patching, but absent EPSS/KEV/POC it is not confirmed as an active, widespread priority - prioritize based on whether Content Credentials integrity is security-relevant to your deployment. |
| Exploit ScenarioDerived | An attacker sends crafted, malformed input to an application that uses the CAI Content Credentials SDK, and because input validation is improper, the SDK's integrity/security checks are bypassed, allowing the attacker to write or alter content-credential data without authorization. Because the CVSS vector is AV:N/PR:N/UI:N, this can be attempted remotely without authentication or user interaction. No public proof-of-concept is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Improper input validation in the CAI Content Credentials SDK allows a remote, unauthenticated attacker to feed crafted input into the SDK's processing path and bypass its integrity and security checks, resulting in unauthorized write access to Content Credentials data. Adobe PSIRT rates the issue CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), meaning no privileges, no authentication, and no user interaction are required, and the impact is confined to integrity - forged or tampered provenance data - with no direct confidentiality or availability loss. Exposure is the limiting factor: since the SDK is a specialized provenance component, real risk depends on whether a downstream application actually accepts untrusted input through the vulnerable code path; there is no public exploit identified at time of analysis and no evidence of active exploitation.
RemediationAI
Consult Adobe advisory APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html) for the vendor-released fixed SDK build and update every embedded instance - the input data does not specify an exact fix version, so no patched version number is asserted here, and patch availability should be treated as available per vendor advisory until the bulletin confirms otherwise. Until the updated SDK is deployed, the highest-value compensating control is exposure reduction: do not route untrusted, third-party Content Credentials into the SDK's parsing/validation path, and if it is already reachable, place that endpoint behind network segmentation or an authenticated reverse proxy - the trade-off is that this adds authentication friction to a flow that the vulnerability itself reaches unauthenticated, and it does nothing against an attacker who already has a foothold on the internal network. Add a strict schema/type validation and size-limit layer in front of the SDK so malformed or unexpected manifest fields are rejected before they reach the vulnerable validation code; this is cheap but only catches input shapes you anticipate, so it is defense-in-depth rather than a fix. Where the SDK's output is used to assert authenticity, treat write operations to Content Credentials stores as untrusted until verified out-of-band (for example, re-verifying credentials against an independent signing/trust root) and monitor for unusual manifest writes or credential replacements, accepting the added verification latency and possible false positives. Note that the CVSS vector is integrity-only (C:N/A:N), so these measures should be prioritized around authenticity of written data rather than availability or data-loss scenarios.
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 flaw is classified as CWE-20 (Improper Input Validation) in the CAI Content Credentials SDK, the component that handles Content Credentials - cryptographically signed provenance and authenticity metadata typically associated with the C2PA specification for images, video, and other media. Because the SDK fails to properly validate attacker-supplied input, an attacker can drive the code past the checks that are meant to be a security feature (the integrity/verification boundary), producing a security-feature bypass whose outcome is unauthorized write access rather than code execution or data disclosure. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N confirms the attack is network-reachable with low complexity, requires no privileges (PR:N) and no user interaction (UI:N), and is scoped to integrity only (I:H with C:N/A:N), so the realistic worst case is forged, tampered, or spoofed Credentials that downstream consumers may trust. The input data does not supply CPE strings or an enumerated set of affected builds, so exact product/version matching must be derived from Adobe's advisory APSB26-163, and any application or service that embeds the vulnerable SDK and exposes its input-processing path inherits the exposure.
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:H/A:N
Network-reachable, low-complexity, unauthenticated bypass with no user interaction yielding unauthorized writes; integrity-only impact (I:H), with no confidentiality or availability effect.
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. Exploitation of this issue does not require user interaction.
Executive ViewAI
The CAI Content Credentials SDK contains a high-severity improper input validation flaw (CVE-2026-100113) that allows remote, unauthenticated attackers to bypass integrity checks and write unauthorized data to Content Credentials. Organizations using this SDK in applications that accept untrusted input could face forged or tampered provenance data, undermining content authenticity and trust. With no vendor-released patch identified at time of analysis, leadership should prioritize identifying affected systems and implementing interim mitigations to protect their brand and compliance posture.
Implement strict input validation and sanitization for all data processed by the SDK; isolate the SDK in a sandboxed environment with least privilege; restrict network access to the vulnerable code path; monitor for unauthorized writes to Content Credentials data; and engage the vendor for patch timeline and interim mitigations.
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
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
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exh
Exploit-DB