CVE-2026-104345: CAI Content Credentials Auth Bypass Flaw

CVE-2026-104345 Overview

CVE-2026-104345 is an improper input validation vulnerability [CWE-20] affecting Adobe CAI Content Credentials. The flaw allows a remote attacker to bypass security controls and obtain unauthorized write access without any user interaction. Adobe disclosed the issue in security advisory APSB26-163.

The vulnerability is network-exploitable and requires no privileges or user interaction. Integrity impact is high, while confidentiality and availability are not directly affected. Organizations using the Content Credentials SDK to validate provenance metadata should prioritize patching to prevent tampering with signed content attestations.

Critical Impact
Unauthenticated attackers can bypass security feature enforcement over the network to gain unauthorized write access, undermining the integrity of content credential attestations.

Affected Products

Adobe CAI Content Credentials SDK
Content Credentials implementations relying on the affected SDK validation routines
Downstream applications consuming Content Credentials provenance metadata

Discovery Timeline

2026-10-13 - CVE-2026-104345 published to the National Vulnerability Database
2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-104345

Vulnerability Analysis

The Coalition for Content Provenance and Authenticity (CAI) Content Credentials SDK validates provenance metadata attached to digital assets. The vulnerability stems from improper input validation [CWE-20] in the SDK's processing path. An attacker can craft input that the SDK fails to validate correctly, causing enforcement logic to be bypassed.

Because the attack vector is network-based and requires no authentication or user interaction, exploitation can be delivered through any workflow that accepts Content Credentials data. Successful exploitation grants unauthorized write access, allowing modification of state that should be protected by the SDK's security feature.

The EPSS score of 0.498% reflects limited observed exploitation signals at publication time. However, the integrity impact on provenance workflows makes this a priority fix for publishers, media platforms, and generative AI providers that rely on Content Credentials.

Root Cause

The root cause is insufficient validation of attacker-controlled input within the Content Credentials SDK. The SDK accepts data that should be rejected or sanitized, allowing the attacker to reach code paths that enforce security decisions on unverified input. This permits a bypass of the intended security feature.

Attack Vector

Exploitation occurs over the network against any application or service that processes Content Credentials via the vulnerable SDK. The attacker submits crafted content or metadata, triggering the input validation flaw and bypassing the security feature to perform unauthorized write operations. See the Adobe Security Advisory APSB26-163 for vendor-specific details.

Detection Methods for CVE-2026-104345

Indicators of Compromise

Unexpected modifications to Content Credentials manifests or provenance assertions on signed assets
Validation log entries showing successful processing of malformed or non-conformant Content Credentials payloads
Write operations to Content Credentials stores from processes or principals that normally only perform reads

Detection Strategies

Compare Content Credentials manifest hashes against known-good baselines captured at publish time
Alert on SDK validation routines that return success for inputs that fail stricter secondary validators
Correlate network requests delivering Content Credentials payloads with downstream write operations on the asset store

Monitoring Recommendations

Enable verbose logging on Content Credentials SDK validation and signing paths
Forward application logs to a centralized SIEM for anomaly analysis across ingestion workloads
Monitor outbound integrity-signing requests for abnormal volume or principal patterns

How to Mitigate CVE-2026-104345

Immediate Actions Required

Inventory all applications and services that embed or depend on the Adobe CAI Content Credentials SDK
Apply the fixed SDK version referenced in Adobe Security Advisory APSB26-163
Rebuild and redeploy downstream applications after updating the SDK dependency
Audit recent Content Credentials write operations for signs of tampering during the exposure window

Patch Information

Adobe published fix guidance in advisory APSB26-163. Review the Adobe Security Advisory APSB26-163 for the specific fixed SDK versions and upgrade instructions. Update dependency manifests to pin to the patched release and verify integrity of the resolved package.

Workarounds

Restrict network reachability of services that process Content Credentials to trusted producers only
Add a secondary validation layer that re-verifies Content Credentials manifests before any write operation
Enforce least-privilege access on Content Credentials stores so compromised SDK paths cannot escalate to broad writes