EUVD-2026-100729
GHSA-8c73-x8vv-v693
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain forged or invalid certificate
-
ExploitPresent to Content Credentials validation path
-
ExecutionBypass improper certificate validation (CWE-295)
-
ImpactGain unauthorized write access to trusted content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
|
| Exploitation Conditions | Exploitation requires the attacker to exercise the SDK's certificate/trust validation path for Content Credentials - specifically to present a forged, self-signed, or otherwise invalid signing certificate (or a crafted C2PA manifest) that the SDK accepts due to improper validation (CWE-295). No user interaction is required (UI:N). The practical limiting factor is that the attacker must be able to deliver such content into a workflow that validates it with the vulnerable SDK, or occupy a trust/transport position where a malicious certificate is presented; this is narrower than the raw AV:N score suggests. Impact is confined to integrity (unauthorized write/forged provenance); no confidentiality or availability loss is indicated. |
| Impact | Signals are moderately consistent but not alarming. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5 HIGH) indicates a network-reachable, low-complexity, unauthenticated flaw affecting integrity only - matching CWE-295 improper certificate validation that lets an attacker bypass a trust check. No CISA KEV listing, no public POC, and no EPSS score are present in the input, so there is no evidence of active or imminent widespread exploitation; status is best described as 'no public exploit identified at time of analysis.' A key tension to verify: the vector claims AV:N/PR:N, but improper certificate validation flaws typically require the attacker to be positioned to present a forged/invalid certificate (e.g., man-in-the-middle or supplying a crafted signed manifest), which narrows the realistic attacker population below what a pure remote-unauthenticated score implies - verify the exact trigger path with Adobe's advisory. Overall this is a credible integrity-bypass issue to patch on normal cadence, not a drop-everything emergency, given the absence of KEV/POC/EPSS corroboration and the specialized nature of the affected SDK. |
| Exploit ScenarioDerived | An attacker positioned to supply or intercept signed content (e.g., a forged Content Credentials manifest or a man-in-the-middle TLS position) presents a certificate that the SDK fails to validate properly. Because validation is bypassed, the attacker's content is accepted as trusted, enabling unauthorized write/injection of provenance data without any user interaction. 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 certificate validation (CWE-295) in the CAI/Adobe Content Credentials SDK allows an unauthenticated remote attacker to have forged or self-signed signing certificates accepted during C2PA manifest verification, bypassing the provenance trust check and enabling unauthorized write (integrity) impact - CVSS 3.1 base 7.5, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. No user interaction is required, but exploitation is not automatic: the attacker must get crafted content into a workflow that validates it with the vulnerable SDK, or occupy a trust/transport position from which a malicious certificate is presented, which is narrower in practice than the network-vector score implies. There is no CISA KEV listing and no public exploit identified at time of analysis; impact is confined to integrity, with no confidentiality or availability loss indicated.
RemediationAI
Patch available per vendor advisory: Adobe security bulletin APSB26-163 at https://www.adobe.com/trust/security/products/content-credentials-sdk/apsb26-163.html documents the fixed Content Credentials SDK release, but no exact fix version was supplied in the input data, so the precise build number must be read directly from that bulletin before upgrading and integrators should rebuild and re-test any application that bundles the SDK. Where immediate upgrade is not possible, the most effective compensating control is to perform independent certificate validation above the SDK: pin the accepted trust anchors, reject self-signed or non-chaining certificates, and verify the certificate's issuer and key-usage against the expected signer - the trade-off is that overly strict pinning can break legitimate signatures during CA rotation and require ongoing trust-list maintenance. A second option is to quarantine or refuse to process untrusted C2PA manifests and unverified content at ingest, treating all externally sourced provenance claims as untrusted and surfacing them as unverified rather than authoritative; this reduces exposure but degrades the product's verification feature for external content. Restricting which systems may submit content into validation workflows, or gating it behind a broker that presents only vetted certificates, narrows the delivery surface implied by the network vector, though it does not fix the underlying validation defect. Given the integrity-only, provenance-forgery impact and the absence of confirmed exploitation, remediation can be scheduled with normal patch cadence, prioritizing any deployment that uses Content Credentials output as a trust signal.
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
CWE-295 (Improper Certificate Validation) is the root-cause class: the SDK's certificate/trust validation path for Content Credentials does not correctly verify that a signing certificate chains to a trusted anchor, is not self-signed or otherwise invalid, or is authorized for the asserted signer. In Content Credentials the signing identity travels inside a C2PA manifest attached to the asset, so an attacker who can supply a manifest can also supply the accompanying X.509 certificate material; if validation is weak, the forged provenance record is accepted as authentic. The CVSS vector places this as a remote, unauthenticated, no-UI issue with scope unchanged, meaning the bypass stays within the SDK's security authority rather than pivoting to the host, and only integrity (I:H) is affected - attackers gain unauthorized write/forged-provenance capability, not data disclosure or denial of service. Because the flaw lives in the trust-evaluation logic rather than in cryptographic primitives, detection depends on whether the validating application enforces its own trust-anchor policy above the SDK. The single reference available is Adobe's advisory APSB26-163 for the Content Credentials SDK, which is the applicable vendor source; no CPE strings or version ranges were supplied with the input data, so affected builds must be confirmed against that bulletin.
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
Improper cert validation is network-reachable and needs no credentials or user action (AV:N/AC:L/PR:N/UI:N); only integrity is affected via trust bypass, so C:N/I:H/A:N, scope unchanged.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
CAI Content Credentials is affected by an Improper Certificate Validation 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
The CAI/Adobe Content Credentials SDK - the component responsible for verifying C2PA provenance manifests - can be made to accept forged or self-signed signing certificates, so content falsely asserting its origin and integrity may pass validation. Every function that leans on Content Credentials as proof of authenticity, including media production, legal and rights enforcement, brand and marketing publishing, and trust-and-safety moderation, loses a guarantee it currently treats as reliable. No vendor patch has been identified at time of analysis and there is no public exploit identified at time of analysis, but the flaw weakens the core trust promise of the product, so leadership should treat it as a provenance-integrity risk affecting decisions rather than a conventional network intrusion risk.
No vendor-released patch identified at time of analysis. Interim mitigations: disable or gate automatic C2PA manifest verification in non-essential workflows; never allow a Content Credentials result to be the sole basis for a trust, publication, rights, or payment decision; enforce an explicit trusted-issuer allowlist or certificate pinning ahead of SDK verification; log and alert on self-signed or unexpected issuer certificates presented in submitted manifests; and restrict which external or untrusted content is routed into verification pipelines. Exploitation is unauthenticated and requires no user interaction, though an attacker must still place crafted content into a validating workflow or occupy a trust/transport position presenting a malicious certificate.
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