EUVD-2026-100716
GHSA-gm27-q289-gqx3
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK-backed parsing 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 an application using the CAI Content Credentials SDK accept and process attacker-supplied Content Credentials/C2PA content through the vulnerable parsing or verification path; the resource-exhaustion condition is triggered by that untrusted input. Per CVSS (AV:N/AC:L/PR:N/UI:N), no authentication, no user interaction, and no special configuration are required once the input reaches the SDK - so the practical limiting factor is network exposure of a component that ingests untrusted content through this SDK. Impact is confined to availability (C:N/I:N); there is no data compromise. The exact input structure or SDK operation that triggers exhaustion is not specified in the available data and should be confirmed via Adobe advisory APSB26-163. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is internally consistent with the description: a remotely reachable, low-complexity, unauthenticated flaw with no user interaction, impacting availability only (CWE-400, Uncontrolled Resource Consumption). The 7.5 score is driven entirely by the high availability impact - there is no confidentiality or integrity exposure, so this is a pure denial-of-service issue rather than a path to code execution or data theft. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or weaponization; exploitation status is best described as no public exploit identified at time of analysis. Net assessment: a legitimately network-exploitable DoS worth patching, but not an emergency on par with an RCE - real-world urgency depends on whether the SDK processes attacker-supplied content in an internet-facing service. The one ambiguity is the exact trigger: the description says resources are exhausted but does not name the specific input or operation, so the precise exploitation path should be verified against Adobe advisory APSB26-163. |
| Exploit ScenarioDerived | An attacker submits specially crafted content (e.g., a malformed or maliciously structured Content Credentials/C2PA asset) to an application that uses the CAI Content Credentials SDK to parse or verify it. Processing the input causes uncontrolled resource consumption (CPU, memory, or similar), exhausting system resources and rendering the application unresponsive. No authentication or user interaction is required (AV:N/PR:N/UI:N), and 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
Uncontrolled resource consumption in the Adobe CAI Content Credentials SDK lets unauthenticated, remote attackers exhaust system resources and drive an application into denial-of-service by feeding it specially crafted Content Credentials/C2PA data. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), the flaw is network-reachable, low-complexity, requires no authentication and no user interaction, and affects availability only - there is no confidentiality or integrity impact, so no data compromise is expected. The practical precondition is that a deployed application actually accepts and processes attacker-supplied content through this SDK's parsing or verification path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the exact input structure that triggers exhaustion is not documented in the available data.
RemediationAI
The primary action is to apply the fixed SDK release identified in Adobe security bulletin APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html), rebuild any application that statically or dynamically links the Content Credentials SDK, and re-deploy; because the advisory is the only version source in the available data, confirm the exact patched version there rather than assuming one. Until the update is in place, apply compensating controls at the ingestion boundary where untrusted Content Credentials enter the SDK: cap request and manifest size and reject oversized payloads before parsing (trade-off: legitimate large manifests may be refused), enforce per-client rate and concurrency limits on the endpoint that processes credentials, and run parsing/verification in an isolated worker with hard memory-cap, CPU-time, and request-timeout enforcement so that exhaustion is contained to a single disposable process instead of the whole service (trade-off: added latency and infrastructure complexity, and a killed worker still fails that one request). Longer timeouts or unbounded thread pools undermine these controls; keep the SDK path off the public internet where it is not required, and monitor for spikes in CPU, memory, or worker restarts as an indicator of attempted exploitation.
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 vulnerability is an instance of CWE-400, Uncontrolled Resource Consumption, in the Content Authenticity Initiative (CAI) Content Credentials SDK - the library Adobe provides for generating and validating C2PA Content Credentials manifests (provenance/cryptographic-attestation metadata embedded alongside media). The weakness class arises when the SDK's parsing or verification logic fails to bound the work it performs on untrusted input: attacker-controlled manifests can drive disproportionate consumption of CPU, memory, or I/O (for example through oversized or pathologically structured manifest fields, deeply nested or repeated assertions, or large numbers of embedded resources), so a single request can starve the hosting process or worker of resources. The CVSS vector's AV:N/AC:L/PR:N/UI:N profile means the entire exposure surface is the point at which untrusted Content Credentials enter the SDK - no credentials, no victim interaction, and no non-default configuration are required once that input reaches the vulnerable code path. The Scope:Unchanged / C:N / I:N / A:H combination confines the outcome to degradation or loss of availability of the consuming application, consistent with the CWE-400 classification. CPE data was not supplied in the available intelligence, so affected builds should be enumerated from Adobe advisory APSB26-163 rather than inferred here.
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
Untrusted input reaches the SDK over the network without authentication or interaction (AV:N/AC:L/PR:N/UI:N); impact is availability-only resource exhaustion (A:H, C:N/I:N), scope unchanged.
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 flaw in the Adobe CAI Content Credentials SDK allows any unauthenticated remote party to exhaust system resources and knock over applications that parse Content Credentials/C2PA data, but only where those applications actually accept attacker-supplied content. No data can be read or altered, so the exposure is service availability rather than confidentiality or integrity: teams running content-verification, media-ingest, or publishing pipelines on this SDK could see processing outages and degraded customer-facing services. Leadership should care because no vendor patch is available and the mitigation burden falls on internal engineering and operations until Adobe releases a fix.
No vendor-released patch identified at time of analysis; the flaw is unauthenticated and network-reachable with no public exploit identified at time of analysis, so interim mitigations are input-size and complexity limits on C2PA/Content Credentials payloads, strict parse timeouts and memory/CPU ceilings, process isolation with container resource quotas, edge throttling or blocking of untrusted Content Credentials submissions, and disabling SDK-based verification where it is not operationally required until Adobe ships a fixed version.
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
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