EUVD-2026-100740
GHSA-rxm6-8qg9-5wv7
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach SDK-backed processing 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 | The affected component is the CAI Content Credentials SDK, so exploitation requires that a target application or service actually uses the SDK to ingest and process attacker-supplied Content Credentials data (such as C2PA manifests or embedded asset metadata) over a reachable interface. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, no user interaction, and no non-default configuration are required once such a processing path is exposed. The primary limiting factor is exposure: the risk is realized only where the SDK's parsing/verification functionality is reachable by untrusted input (e.g., an internet-facing upload or verification endpoint); the provided data does not specify a minimum vulnerable version or the exact API/function that triggers the exhaustion, so defenders should confirm affected versions and the triggering surface against APSB26-163. |
| Impact | The CVSS 3.1 base score of 7.5 is driven entirely by availability impact (C:N/I:N/A:H) with a fully remote, low-complexity, unauthenticated, no-interaction vector (AV:N/AC:L/PR:N/UI:N). This is a classic uncontrolled-resource-consumption DoS (CWE-400): no data is read or altered, only service availability is affected, which is why confidentiality and integrity are rated None. No EPSS score, CISA KEV listing, POC, or SSVC decision data was provided in the input, so exploitation-likelihood and automatability signals are absent and cannot be weighed against the CVSS score. The CVSS vector and the description are consistent (both imply remote, no-user-interaction exploitation), so there is no network-vs-local conflict to flag. Overall this reads as a genuine but single-dimension (availability-only) remote DoS: the raw score is high because the vector is clean and unauthenticated, but real-world urgency depends on how exposed the SDK's processing surface is to attacker-supplied content and is tempered by the absence of any evidence of active exploitation or public exploit code. Treat as a meaningful availability risk for internet-facing services built on the SDK, but not as a confirmed-exploited emergency. |
| Exploit ScenarioDerived | An attacker submits specially crafted Content Credentials data (e.g., a malformed or maliciously structured C2PA manifest/asset) to a service or application that uses the CAI Content Credentials SDK to parse or verify it. Processing the input consumes excessive CPU or memory, exhausting system resources and rendering the application unresponsive to legitimate users. No authentication or user interaction is required; no public exploit code was 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
Denial of service in the CAI Content Credentials SDK allows remote, unauthenticated attackers to exhaust system resources by supplying crafted Content Credentials data (such as C2PA manifests or embedded asset metadata) for parsing or verification, with no user interaction required. The CVSS 3.1 base score of 7.5 is driven entirely by availability impact (C:N/I:N/A:H) under a fully remote, low-complexity vector (AV:N/AC:L/PR:N/UI:N), meaning integrity and confidentiality are unaffected. Risk is contingent on exposure: only applications or services that actually ingest untrusted Content Credentials input through a reachable interface are at risk, and no public exploit has been identified at time of analysis. Note that no KEV listing or public proof-of-concept is present in the available intelligence, so the practical threat is best characterized as a reliable availability-degradation vector once a vulnerable processing path is reachable rather than as an observed attack campaign.
RemediationAI
No vendor-released patch version could be confirmed from the provided data - the only reference is Adobe security bulletin APSB26-163 (https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html), which should be treated as the primary source for the fixed SDK release and the definitive affected-version list; upgrade to the version named there as soon as it can be validated in a test environment. Until that fix is applied, apply compensating controls targeted at the exhaustion primitive rather than generic hardening: cap the size and nesting depth of accepted C2PA manifests and embedded metadata at the ingress layer and reject anything exceeding the limit, since overly aggressive caps can cause legitimate Content Credentials to fail verification and must be tuned against real asset traffic; enforce per-request wall-clock timeouts and memory/CPU ceilings around the parsing and verification calls so a single malicious payload cannot consume a worker indefinitely; rate-limit or queue untrusted verification requests per client and isolate SDK processing in a sandboxed worker or sidecar with hard resource quotas so exhaustion degrades only that pool rather than the whole application; and, where Content Credentials verification is not a required business function, disable or remove the untrusted-input ingestion path entirely, accepting the loss of provenance-checking capability. Post-fix, monitor memory and CPU on hosts that perform verification to detect renewed resource-exhaustion patterns.
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 Adobe's CAI (Content Authenticity Initiative) Content Credentials SDK, the library used to parse, validate and verify C2PA Content Credentials manifests and the provenance metadata embedded in media assets. The root cause class is an absence of effective bounds on the resources consumed while processing attacker-controlled input: parsing, manifest validation or signature/claim verification paths can be driven to allocate disproportionate memory, CPU or similar resources relative to the size and complexity of the supplied input, which terminates in an application denial-of-service condition. Because the affected capability is an SDK rather than a standalone service, the attack surface is inherited by whatever host product embeds it - anything that accepts externally supplied images, manifests or Content Credentials payloads for verification. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H confirms network reachability, low attack complexity, no privileges required and no user interaction, with scope unchanged and impact confined to availability; the provided data does not identify the minimum vulnerable SDK version or the specific API/function that triggers the exhaustion.
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
Remote parsing of untrusted content needs no auth or interaction (AV:N/AC:L/PR:N/UI:N); impact is availability-only resource exhaustion within one component, so C:N/I:N/A:H and S:U.
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 availability flaw in the CAI Content Credentials SDK allows anyone able to reach a service that parses or verifies Content Credentials data - C2PA manifests or embedded asset metadata - to force that service to consume excessive system resources with no credentials or user interaction required. The exposure is confined to externally reachable content-provenance pipelines built on this SDK; data confidentiality and integrity are unaffected. Leadership should care because a sustained resource-exhaustion condition on a public-facing authenticity-verification service can disrupt customer-facing workflows and erode confidence in the digital provenance signals we rely on, although no public exploit has been identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network reachability of Content Credentials parsing/verification endpoints to trusted clients; enforce authentication or allow-listing at the ingress where feasible; apply strict request-size limits, parsing timeouts, and per-client rate limiting; isolate the parsing workload with CPU/memory quotas, bounded worker concurrency, and queue depth caps; deploy circuit breakers and automatic restart for affected services so resource exhaustion cannot cascade to dependent systems; reject or sandbox oversized or malformed C2PA manifests and embedded metadata before processing; monitor for parsing failures and resource-consumption anomalies to detect abuse attempts.
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
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