EUVD-2026-100725
GHSA-q2vj-g663-c6wj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK-backed content endpoint
-
DeliverySubmit crafted Content Credentials input
-
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 the target application feed attacker-controlled input - a crafted media file or embedded Content Credentials/C2PA manifest - into the CAI Content Credentials SDK's parsing or verification path. The practical attack surface is therefore any service that ingests, verifies, or displays Content Credentials on untrusted uploads. The CVSS vector (PR:N/UI:N) indicates no authentication or user interaction is needed once such input reaches the SDK. The principal LIMITING factor is exposure: deployments that only process trusted, first-party content, or that run the SDK offline/batch without network-reachable upload paths, face substantially reduced real-world risk despite the AV:N rating. Impact is confined to availability (application DoS); no code execution or data disclosure. |
| Impact | This is a network-exploitable, unauthenticated denial-of-service flaw (CVSS:3.1 AV:N/AC:L/PR:N/UI:N, A:H only) in the Adobe CAI Content Credentials SDK, scored 7.5 (High). The CVSS vector is internally consistent with the CWE-400 (Uncontrolled Resource Consumption) classification and the description - no confidentiality or integrity impact, availability-only, no user interaction. However, several key prioritization signals are MISSING from the input: there is no EPSS score, no CISA KEV listing, and no POC indicator, so exploitation status is 'no public exploit identified at time of analysis.' The absence of KEV/EPSS data means real-world exploitation likelihood cannot be quantified from the provided intelligence. On balance this is a genuine but moderate-priority issue: the low attack complexity and lack of authentication make it easy to trigger IF the SDK is exposed to attacker-supplied content, but the impact ceiling is availability loss only (no RCE, no data exposure), and real risk is heavily gated by whether a given deployment actually exposes the SDK to untrusted input (see exploitation_conditions). One caveat to verify: AV:N assumes the SDK processes network-reachable or uploaded content; for an embedded/offline SDK integration the practical vector may be closer to local - confirm against your deployment model. |
| Exploit ScenarioDerived | An attacker submits a specially crafted media asset or Content Credentials manifest to an application that uses the CAI Content Credentials SDK to parse or verify provenance data. Parsing the malicious input triggers uncontrolled resource consumption (CPU, memory, or similar), exhausting system resources and rendering the application unavailable. No authentication or user interaction is required, but no public exploit code has been 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
Application denial-of-service in the Adobe CAI Content Credentials SDK lets unauthenticated remote attackers exhaust system resources by supplying crafted media files or embedded C2PA/Content Credentials manifests that reach the SDK's parsing or verification path, degrading or halting the consuming application (CVSS:3.1 AV:N/AC:L/PR:N/UI:N/A:H; 7.5 High). Impact is confined to availability - no code execution, privilege escalation, or data disclosure - and real-world risk is heavily gated by exposure, since a service must actually ingest untrusted Content Credentials input for the flaw to be reachable; deployments that only process trusted first-party content or run the SDK offline in batch mode face substantially reduced risk. No public exploit identified at time of analysis.
RemediationAI
Patch available per vendor advisory: apply the fixed release documented in Adobe APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html); the input data does not specify an exact version string, so confirm the patched build from that bulletin. If immediate patching is not possible, apply targeted compensating controls: enforce strict upload size, manifest count, and nesting-depth limits on any Content Credentials input, and reject oversized or deeply nested C2PA manifests (trade-off: may reject legitimate large assets and requires baseline tuning). Run SDK parsing/verification in a memory-, CPU-, and time-constrained sandbox or container so a single malicious file cannot exhaust host resources (trade-off: added latency and possible false timeouts for legitimate complex files). Rate-limit and queue verification requests, and place the ingesting service behind a resource-aware reverse proxy (trade-off: throughput reduction under load). Where Content Credentials processing is not business-critical, disable or gate verification for untrusted upload paths until patched, accepting the loss of provenance features. Because exploitation requires attacker-controlled content to reach the SDK, restricting network exposure of upload/verification endpoints reduces the attack surface but does not eliminate risk from authenticated or internal ingestion paths.
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 an uncontrolled resource consumption issue (CWE-400) in the Adobe Content Authenticity Initiative (CAI) Content Credentials SDK, which implements parsing and verification of C2PA (Coalition for Content Provenance and Authenticity) manifests embedded in media files. Because the SDK is designed to read attacker-influencable provenance metadata, a crafted file or manifest can drive unbounded memory, CPU, or handle consumption during parsing/verification. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms a remote, unauthenticated trigger with no user interaction once malicious input reaches the SDK, and an availability-only impact with no confidentiality or integrity loss. The practical attack surface is any component - web upload endpoint, batch pipeline, or media processing service - that ingests, verifies, or displays Content Credentials from untrusted sources; the rating does not imply that arbitrary internet clients can reach the SDK directly.
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
Crafted input parsed by the SDK triggers resource exhaustion with no auth or interaction (AV:N/AC:L/PR:N/UI:N); availability-only impact (A:H, C:N/I:N) matches CWE-400 DoS.
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
A high-severity denial-of-service flaw in the Adobe CAI Content Credentials SDK allows unauthenticated remote attackers to degrade or halt any application that parses untrusted media files or embedded C2PA/Content Credentials manifests, and Adobe has not released a fixed version. Because the SDK is typically embedded inside third-party products rather than exposed directly, the teams most exposed are those operating content-ingestion pipelines, media upload services, or customer-facing platforms that accept externally supplied files. The impact is limited to availability - there is no code execution, privilege escalation, or data disclosure - and risk is heavily gated by whether an application actually ingests untrusted Content Credentials input, but for those that do, sustained resource exhaustion can take a production service offline until patched.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict Content Credentials and C2PA manifest ingestion to trusted first-party content where feasible and keep the SDK in offline batch mode for trusted-only workflows; process any untrusted media in isolated containers or sandboxes with strict CPU, memory, and wall-clock time quotas; enforce maximum file size, manifest depth, and node-count limits at the ingestion boundary and reject malformed or abnormally nested manifests; apply rate limiting, queuing with backpressure, and hard request timeouts in front of parsing endpoints; require authentication or additional controls for anonymous uploads; and monitor for resource exhaustion, crash loops, and latency spikes so that abusive inputs can be blocked quickly.
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
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
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exh
Exploit-DB