EUVD-2026-100726
GHSA-rvgq-wjcq-9rfw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK-backed endpoint over network
-
ExploitBypass access-control check
-
ExecutionGain unauthorized write access
-
ImpactTamper with content credentials
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 | No special conditions beyond network reachability - the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates remote, unauthenticated exploitation with no user interaction against an application using the CAI Content Credentials SDK, abusing an improper access-control check to gain write access. The principal limiting factor is impact scope, not reachability: the flaw yields integrity impact only (unauthorized write/tampering, I:H) with no confidentiality (C:N) or availability (A:N) consequence, so exposure depends on how much the deploying application trusts Content Credentials data for provenance or security decisions. Exact affected SDK versions and any configuration dependencies are not specified in the supplied data and should be verified against Adobe advisory APSB26-163. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5 HIGH) describes a cleanly remote, low-complexity, unauthenticated flaw with no user interaction, but the impact is scoped entirely to integrity (I:H) with no confidentiality or availability consequence - consistent with the description's 'unauthorized write access' via a security-feature/access-control bypass (CWE-284). This is a genuinely easy-to-reach bug by the CVSS metrics, but the business risk is bounded: an attacker can tamper with or forge writes (e.g. content-provenance/credential data) but cannot read sensitive data or disrupt availability through this issue alone. No EPSS score, 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. Net: the metrics justify prompt patching for any deployment that relies on Content Credentials integrity, but this is not (on current evidence) a mass-exploited, high-urgency item - treat as a real but integrity-scoped priority rather than a widespread emergency. No conflicting signals were observed between the CVSS vector and the description; both point to remote, no-interaction, write-oriented abuse. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends crafted requests to an application built on the CAI Content Credentials SDK and leverages the improper access control to bypass the intended security check, obtaining write access they should not have. They use this to tamper with or inject content-credential/provenance data without needing any valid user to click or interact. 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 CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass a security check and gain unauthorized write access, with no user interaction required (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N). The impact is scoped entirely to integrity - the assessed vector shows no confidentiality or availability effect - so practical exposure depends on how much a deploying application trusts Content Credentials data for provenance or security decisions. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; Adobe advisory APSB26-163 is the authoritative source for affected and fixed SDK versions.
RemediationAI
Adobe's PSIRT advisory APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html) is the primary remediation reference; patch availability is indicated by that advisory, but the supplied data does not state an exact fixed SDK version, so identify and install the patched Content Credentials SDK release named there and verify the build number after upgrade. Until the patch is applied, treat all Content Credentials data as untrusted input: independently validate credential manifests and signatures before acting on them, and do not derive authorization or provenance-trust decisions solely from values written through the SDK, since the defect yields unauthorized write access with integrity-only impact (I:H, C:N, A:N). Practical compensating controls are to restrict network access to endpoints that ingest or update credential data via caller allow-listing, enforce authorization server-side independently of the SDK, and alert on unexpected credential modifications - with the trade-off of added integration effort and potential breakage of legitimate ingestion flows if callers are over-restricted; disabling credential-writing functionality entirely removes the exposure but breaks provenance signing and ingestion features.
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-284 (Improper Access Control) in Adobe's CAI Content Credentials implementation, which underpins Content Credentials - cryptographically signed provenance manifests and assertions used to attest the origin and edit history of digital content. Because the access-control check governing write operations (creation or modification of credential data the SDK is meant to protect) is missing or improperly enforced, a remote caller with network reachability can perform writes it should not be authorized to make, which Adobe labels a security feature bypass and an authentication bypass. The assessed vector is consistent with a cleanly remote, low-complexity, unauthenticated condition (AV:N/AC:L/PR:N/UI:N) whose only material impact is integrity (I:H) with no confidentiality or availability consequence; this means the security significance materializes where downstream consumers treat Content Credentials output as trustworthy provenance. No CPE identifiers, exact affected SDK versions, or configuration dependencies were supplied, and Adobe PSIRT (psirt@adobe.com) is the reporting party.
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
Description confirms remote access-control bypass with no user interaction and write-only impact, so AV:N/AC:L/PR:N/UI:N with I:H and 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
A security-check bypass in the Adobe CAI Content Credentials SDK allows any remote attacker, with no credentials and no user interaction, to write unauthorized content-provenance data that consuming applications may treat as legitimate. Content Credentials is increasingly used to assert the authenticity and origin of media, so any team that relies on it for provenance or trust decisions carries a direct integrity exposure, while no vendor patch is currently available. Leadership should care because the risk is concentrated in downstream trust decisions rather than in the SDK itself, and remediation depends on changes we control plus vendor timelines we do not.
No vendor-released patch identified at time of analysis. Interim mitigations: treat all Content Credentials data as untrusted input and stop using it as the sole basis for access, publishing, or approval decisions; validate credentials server-side against a defined allowlist of trusted issuers and signing keys instead of accepting embedded assertions; restrict network egress from services that parse credential data; monitor and alert on unexpected or anomalous credential write activity; and track Adobe advisory APSB26-163 for the corrected SDK version and apply it as soon as it is published.
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