EUVD-2026-100743
GHSA-fqpg-7vvr-r67f
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK-backed endpoint over network
-
DeliverySend crafted provenance/credential request
-
ExploitBypass improper access control check
-
ExecutionGain unauthorized write access
-
ImpactTamper with content credential integrity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the vulnerable CAI Content Credentials SDK be integrated into an application that exposes its affected access-controlled operation to attacker-reachable input; per the vector (PR:N/UI:N) no authentication or user interaction is needed. The specific protected feature being bypassed is a security/access-control check guarding write access to content-credential (provenance) data, though the description does not name an exact API, setting, or deployment mode. The practical limiting factor is that this is an SDK rather than a turnkey service: reachability depends entirely on how the integrator wires the SDK (network-facing vs. local/client-side use), and impact is confined to integrity (C:N/A:N) - no data disclosure or denial of service results. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) describes a network-reachable, low-complexity, unauthenticated flaw with no user interaction and a high integrity impact but no confidentiality or availability impact - consistent with an access-control/security-feature bypass that grants unauthorized write access. No EPSS probability, CISA KEV listing, or public POC is present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. This means the 7.5 score is driven entirely by theoretical reachability and ease rather than by any observed real-world activity: treat it as a notable but not emergency-grade issue pending exploitation signals. One caveat to verify: CAI Content Credentials is an SDK/library rather than a standalone network service, so the AV:N rating assumes the SDK is embedded in a network-facing application - actual exposure depends on how a given integrator deploys it, and the raw vector may overstate reachability for offline or client-side usage. Prioritize patching where the SDK handles untrusted content provenance operations in a server/service context. |
| Exploit ScenarioDerived | An attacker sends crafted input to an application that embeds the CAI Content Credentials SDK, abusing the improper access control to bypass the intended security check without authentication or user interaction. This lets them obtain unauthorized write access - for example tampering with or forging content-credential/provenance data - undermining the integrity guarantees the SDK is meant to provide. 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 13, 2026
Improper access control in the Adobe CAI Content Credentials SDK lets unauthenticated, network-reachable attackers bypass a security check and obtain unauthorized write access to content-credential (provenance) data. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) confirms the flaw needs no credentials and no user interaction, and that impact is confined to integrity - there is no confidentiality or availability effect. The practical exposure hinges on integration: this is an SDK, so reachability and real-world impact depend entirely on whether the host application exposes the affected access-controlled operation to attacker-controlled input; no public exploit code and no confirmed active exploitation were identified at time of analysis.
RemediationAI
Apply the fixed SDK release referenced in Adobe's advisory APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html), which is the primary and authoritative remediation for CVE-2026-100114; the exact patched SDK version is not enumerated in the supplied data and should be confirmed directly against the bulletin before upgrading. Because this is a library, patching is not complete until every integrating application is rebuilt and redeployed with the updated SDK, so inventory embedded copies - including transitive and vendored ones - and re-release dependent software. If immediate upgrade is not feasible, do not rely on the SDK's own access-control behavior as the only gate: enforce server-side authorization on any endpoint or handler that triggers content-credential writes, and keep those operations behind an authenticated, trusted boundary rather than exposing them to attacker-reachable input. Where the write path cannot be fronted by an independent authorization layer, disable or remove the affected content-credential write functionality until the patched SDK is deployed - a trade-off that removes provenance-signing capability for that deployment. Note that the flaw is integrity-only (no confidentiality or availability impact), so prioritization can weigh the business value of unauthenticated provenance-data tampering; however, because the vector is PR:N/UI:N with low attack complexity, the practical barrier to abuse is low wherever the SDK is network-exposed.
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 affected component is the CAI (Content Authenticity Initiative) Content Credentials SDK, the library developers embed to create and sign C2PA-style provenance manifests that attest to the origin and edit history of digital media. The root cause is CWE-284, Improper Access Control - a protected operation that should gate write access to content-credential data is either missing an authorization check or applies it incorrectly, so an attacker can reach a write path that should have been denied. Because the vector carries PR:N and UI:N, the bypass is reachable without authentication and without victim interaction once the vulnerable operation is exposed. The vector's C:N/A:N with I:H indicates the failure is a write-integrity problem - an attacker can alter or inject provenance data rather than read protected data or cause a denial of service. Attribution to the SDK rather than a service matters: there is no single hosted endpoint to block, and the vulnerable code path is compiled into whatever application the SDK is integrated into, so the effective attack surface is a function of the integrator's deployment (network-facing service versus local or client-side use).
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
Unauthenticated access-control bypass over network with no user interaction (PR:N/UI:N/AV:N/AC:L); impact is unauthorized write only, so I:H with C:N/A:N.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
CAI Content Credentials is affected by an Improper Access Control 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 Adobe CAI Content Credentials SDK contains a high-severity access-control flaw that lets unauthenticated network attackers write unauthorized changes to content-provenance data, potentially undermining trust in digital content credentials across customer-facing or partner-integrated services. Leadership should care because affected integrations may allow tampering with provenance records, damaging organizational credibility and partner trust even without confidentiality or availability impact. No public exploit identified at time of analysis, and no vendor-released patch is available, so risk must be managed through temporary mitigations and exposure reduction.
No vendor-released patch identified at time of analysis; interim mitigations include network restrictions, application-layer authentication and authorization, least privilege, input validation, WAF/API gateway rules, monitoring for unauthorized provenance writes, and disabling the affected SDK operation where feasible.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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