EUVD-2026-100719
GHSA-mfj9-g945-h3gj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK-backed parsing endpoint
-
DeliverySubmit crafted Content Credentials asset
-
ExploitTrigger uncontrolled resource consumption
-
ExecutionExhaust CPU/memory
-
ImpactApplication denial-of-service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact 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 an application using the CAI Content Credentials SDK accept and process attacker-supplied content (assets or their embedded Content Credentials/C2PA manifest data) through the vulnerable parsing or verification path; the uncontrolled resource consumption is triggered by the malicious input itself. Per the CVSS vector this needs no authentication (PR:N) and no user interaction (UI:N), and is network-reachable (AV:N) with low complexity (AC:L). The practical limiting factor is exposure: because this is an embedded SDK rather than a standalone service, impact is confined to deployments that feed untrusted, externally-sourced content into the SDK - integrations that only process trusted or internally-generated assets are not realistically reachable. Impact is limited to availability (A:H); no confidentiality or integrity compromise occurs. |
| Impact | The signals are moderately consistent but incomplete. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5 HIGH) describes a network-reachable, low-complexity, unauthenticated flaw with no confidentiality or integrity impact and a pure availability impact - a textbook remote DoS, which aligns cleanly with the CWE-400 (Uncontrolled Resource Consumption) classification and the description's 'does not require user interaction.' However, availability-only DoS issues are routinely capped at 7.5 regardless of real-world reachability, so the score overstates priority unless the affected component is exposed to untrusted input in a given deployment. No EPSS score, no CISA KEV listing, no POC, and no SSVC decision data were supplied, so exploitation likelihood cannot be quantified from the input - per the precision rules this is 'no public exploit identified at time of analysis.' Net: this is a credible but not urgent issue - a real, vendor-confirmed availability defect rather than a code-execution or data-exposure threat, and its true priority depends on whether the Content Credentials SDK is processing attacker-controlled assets in a network-facing service. Because the SDK is a library embedded by integrators, actual attack surface varies widely by how each application invokes it. |
| Exploit ScenarioDerived | An attacker submits a specially crafted or malformed content asset (e.g., an image or media file carrying C2PA/Content Credentials manifest data) to an application or service that uses the CAI Content Credentials SDK to parse or verify it. Processing the malicious input causes the SDK to consume excessive memory, CPU, or other resources, exhausting system capacity and rendering the application unresponsive. No public exploit code is identified at time of analysis, and no authentication or user interaction is required (PR:N/UI:N). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Denial of service in Adobe's CAI (Content Authenticity Initiative) Content Credentials SDK stems from uncontrolled resource consumption when the library parses attacker-supplied assets or their embedded Content Credentials / C2PA manifest data. The vulnerable path is network-reachable with low attack complexity and, per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requires no authentication and no user interaction, yielding a 7.5 base score with availability-only impact; confidentiality and integrity are unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied, so practical risk is bounded by exposure: because this is an embedded SDK rather than a standalone service, only integrations that feed untrusted, externally sourced content into the parsing/verification path are realistically reachable, while deployments processing only trusted or internally generated assets are not.
RemediationAI
No exact fixed version is included in the provided data, so the primary action is to consult Adobe's advisory APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html) to identify the corrected SDK release and upgrade it, then rebuild and redeploy every application that embeds the SDK. Until a patched build is confirmed and deployed, apply targeted compensating controls rather than generic hardening: disable or bypass Content Credentials/C2PA manifest parsing and signature verification for untrusted, externally supplied assets (trade-off: provenance validation is lost for those assets and trust decisions must fall back to other signals); enforce strict pre-parse limits on accepted asset size, manifest/JUMBF box size, assertion count, and nesting depth, rejecting anything exceeding them at the ingestion boundary (trade-off: some large but legitimate assets with rich manifests may be rejected); run verification in an isolated worker process or sandbox with hard CPU, memory, and wall-clock quotas plus request timeouts so exhaustion is contained and the worker is restarted rather than the main service (trade-off: added latency, infrastructure cost, and possible false failures on slow or complex legitimate content); and rate-limit or quarantine uploads from unauthenticated sources that reach the verification path. Note that patch availability beyond the referenced advisory is not independently confirmed by the provided data, and no fix version should be assumed without checking the vendor's listing.
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 Content Credentials SDK produced under Adobe's Content Authenticity Initiative, which implements the C2PA (Coalition for Content Provenance and Authenticity) specification for attaching cryptographically signed provenance and editing-history assertions to media files. In a typical integration, the SDK parses a media asset, extracts the embedded C2PA manifest (JUMBF/box-structured metadata, assertion stores, and signature material), and verifies signatures and claim structures before returning trust results. This CVE is classified under CWE-400, Uncontrolled Resource Consumption, meaning the parser or verifier does not adequately bound the resources it commits when consuming attacker-controlled input: a malicious asset or crafted manifest data can drive excessive CPU cycles, memory allocation, file handles, or recursive/iterative processing depth until the host application becomes unresponsive. The CVSS vector confirms the root conduct is remote (AV:N), low complexity (AC:L), unauthenticated (PR:N), and requires no victim interaction (UI:N), with scope unchanged (S:U) and impact confined to availability (A:H) - there is no claimed confidentiality or integrity loss, which is consistent with a resource-exhaustion rather than a memory-corruption or authentication-bypass defect. Because the vulnerable logic lives inside an SDK, the attack surface is inherited by every application that embeds it and exposes asset ingestion to untrusted parties; the deciding factor in real deployments is therefore whether externally supplied content reaches the vulnerable parsing or verification routines, since callers that only process trusted, internally generated assets are not practically exploitable.
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:N/A:H
Unauthenticated remote parsing of untrusted content (AV:N/PR:N/UI:N) with low complexity triggers resource exhaustion; availability-only impact (A:H), no C/I impact.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
CAI Content Credentials is affected by an Uncontrolled Resource Consumption vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to exhaust system resources, resulting in an application denial-of-service condition. Exploitation of this issue does not require user interaction.
Executive ViewAI
Adobe's Content Credentials SDK (CAI) contains a high-severity denial-of-service vulnerability that unauthenticated attackers can trigger by supplying specially crafted assets for parsing. Organizations that process untrusted or externally sourced content through this SDK-such as media forensics platforms, content authenticity services, or public-facing applications-face potential service outages that could disrupt operations and erode trust in content verification workflows. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis; leadership should prioritize identifying affected integrations and implementing interim safeguards.
Implement resource consumption limits (CPU/memory quotas), restrict parsing of untrusted content to isolated environments, enforce network segmentation, and monitor for abnormal resource usage. Where feasible, disable the Content Credentials parsing feature for untrusted inputs or validate credentials from trusted sources only.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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
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
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exh
Exploit-DB