C2Pa Web
Monthly
Server-side request forgery in Adobe Content Credentials (CAI Content Credentials SDK) allows unauthenticated remote attackers to induce the server to make arbitrary outbound requests, potentially reaching internal services and escalating privileges. The CVSS 3.1 base score is 8.6 (HIGH) with a changed scope, high confidentiality impact, and no integrity or availability impact. Exploitation requires no user interaction; no public exploit code has been identified at time of analysis, and the vendor advisory APSB26-163 should be consulted for fixes.
A signature-verification bypass in the CAI Content Credentials SDK allows an unauthenticated, network-reachable attacker to submit content or a token bearing a forged or tampered cryptographic signature that the SDK's verifier accepts, yielding unauthorized write access to systems that rely on that verification as a trust decision. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) the attack needs no credentials and no user interaction, and the assessment confines impact to integrity only, with no confidentiality or availability loss. The practical exposure is narrow but real: only deployments that actually consume the SDK to validate signatures or claims as a security control are affected, and no public exploit code was identified at time of analysis, so this is a genuine integrity issue rather than an acute emergency.
Improper verification of cryptographic signatures in the CAI Content Credentials SDK allows unauthenticated remote attackers to supply forged or improperly signed content credentials that the SDK accepts as authentic, bypassing the security check and gaining unauthorized write access to whatever the SDK's verification verdict gates. The CVSS 3.1 base score is 7.5 (High) under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - an integrity-only signature-verification bypass (CWE-347) with no confidentiality or availability impact, requiring no authentication and no user interaction. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; real-world risk is highest in deployments that make publishing, authorization, or authenticity decisions solely on the SDK's verification result, and negligible where that result is not treated as a trust boundary.
Denial of service in Adobe's CAI (Content Authenticity Initiative) Content Credentials SDK stems from uncontrolled resource consumption when the library parses attacker-supplied assets or their embedded Content Credentials / C2PA manifest data. The vulnerable path is network-reachable with low attack complexity and, per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requires no authentication and no user interaction, yielding a 7.5 base score with availability-only impact; confidentiality and integrity are unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied, so practical risk is bounded by exposure: because this is an embedded SDK rather than a standalone service, only integrations that feed untrusted, externally sourced content into the parsing/verification path are realistically reachable, while deployments processing only trusted or internally generated assets are not.
Denial-of-service in the CAI Content Credentials SDK allows remote unauthenticated attackers to exhaust system resources by supplying crafted Content Credentials data to an application that parses or verifies it. The issue is availability-only (CVSS 3.1 7.5, CWE-400) with no confidentiality or integrity impact, and no public exploit has been identified at time of analysis. Deployments that do not expose SDK-backed parsing to untrusted input face substantially lower real-world risk.
Improper input validation in Adobe's CAI Content Credentials SDK (advisory APSB26-163) lets remote attackers bypass a security feature and obtain unauthorized write access, effectively allowing modification or forgery of protected content-credential data. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) means the flaw is network-reachable, low complexity, unauthenticated, and requires no user interaction, so any application or service that embeds the SDK and exposes its input-processing path to untrusted input is in scope. Impact is confined to integrity (I:H) with no confidentiality or availability loss, and no public exploit code or CISA KEV entry was identified at time of analysis.
Improper verification of cryptographic signatures in Adobe's CAI Content Credentials SDK allows remote, unauthenticated attackers to submit a forged or tampered Content Credentials manifest that the SDK accepts as valid, bypassing a security feature and granting unauthorized write access to credential data (CWE-347; CVSS 3.1 7.5). Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, no credentials and no user interaction are required, and the impact is integrity-only, with confidentiality and availability unaffected; in practice exploitation depends on the vulnerable SDK version being deployed and the consuming application treating signature verification as a trust boundary. This is a moderate-priority integrity issue rather than a top-tier emergency, and no public exploit code or confirmed active exploitation was identified in the available intelligence at time of analysis.
Signature-verification bypass in Adobe Content Credentials SDK allows unauthenticated, network-based attackers to forge or tamper with signed content credentials, bypassing integrity checks to gain unauthorized write access. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) indicates a low-complexity flaw with no user interaction and a pure integrity impact. No public exploit code has been identified at time of analysis, but risk is elevated for applications that rely on the SDK's verification result as a trust or authorization decision. Confirm vulnerable SDK versions against Adobe APSB26-163.
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.
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.
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.
Integer overflow (CWE-190) in the CAI Content Credentials SDK lets unauthenticated remote attackers crash applications that parse externally supplied media or embedded Content Credentials manifests, producing a denial-of-service condition. Affected deployments are those that invoke the SDK against untrusted input - for example services that automatically ingest and verify uploaded or fetched media - while systems that only process trusted, internally generated assets are far less exposed. The vulnerability is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requires no user interaction, causes availability loss only (no disclosure or modification), and no public exploit code has been identified at time of analysis; the vendor advisory is Adobe APSB26-163.
Improper input validation in the Adobe CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass a security control and obtain unauthorized write access. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, any deployment that exposes the vulnerable SDK input path to attacker-supplied content credentials data is reachable without credentials or user interaction, and the impact is integrity-only (C:N/I:H/A:N), meaning tampering with data rather than disclosure or denial of service. Rated CVSS 7.5 (High) and reported directly by Adobe PSIRT via advisory APSB26-163; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Improper input validation in the CAI Content Credentials SDK (Adobe security bulletin APSB26-163) lets unauthenticated remote attackers bypass the SDK's content-credential validation path and gain unauthorized write access, yielding an integrity-only impact (C:N/I:H/A:N, CVSS 7.5). Any deployment that ingests attacker-supplied or externally sourced credential data and runs the vulnerable SDK version through its parse/verify routine is exposed; no authentication (PR:N) and no user interaction (UI:N) are required per the assessed vector, so a default-configured verification service reachable from the network is sufficient. The practical limiting factor is deployment scope rather than a configuration toggle - the flaw only matters where untrusted content actually flows into the SDK - and there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) at the time of writing, which keeps this an elevated but not top-tier priority.
Improper certificate validation in the CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass security features and gain unauthorized write access (CVSS 7.5, High). Exploitation requires the attacker to present a forged or untrusted certificate that the SDK incorrectly accepts, and no user interaction is needed. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Improper certificate validation in Adobe's CAI Content Credentials SDK (Content Credentials SDK) allows remote, unauthenticated attackers to bypass certificate trust checks and gain unauthorized write access, effectively letting them forge or tamper with signed Content Credentials data with no user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5). Impact is bounded to integrity - no confidentiality or availability effect - and only deployments that actually invoke the SDK to validate Content Credentials certificates are exposed. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; exploitation in practice requires the attacker to supply crafted signed content or hold a man-in-the-middle position on the certificate validation path.
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.
Improper input validation in the CAI Content Credentials SDK lets remote, unauthenticated attackers bypass the SDK's security control and obtain unauthorized write access to content-credential data, per Adobe advisory APSB26-163. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) indicates a network-reachable, low-complexity flaw requiring no authentication and no user interaction, with impact confined to integrity - confidentiality and availability are unaffected. Only applications that embed a vulnerable version of the SDK and expose its input-processing/validation path to network-supplied content are affected, and no public exploit code was identified at time of analysis.
Improper input validation in the Adobe CAI Content Credentials SDK lets remote attackers bypass a security feature and gain unauthorized write access to content-credential processing. The flaw is network-reachable, low-complexity, requires no authentication (PR:N) and no user interaction (UI:N), yielding a CVSS 3.1 score of 7.5, but the scored impact is integrity-only (C:N/I:H/A:N) rather than code execution or data disclosure. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; exploitation is contingent on a deployed application embedding the SDK and exposing its C2PA manifest parsing/validation path to attacker-supplied input.
Improper certificate validation in the CAI Content Credentials SDK enables a network-positioned attacker who can intercept TLS connections to bypass security features and gain unauthorized write access. Exploitation requires a man-in-the-middle (MITM) position to supply a forged or invalid certificate that the SDK accepts; the assessed CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, and although the input CVSS 7.5 vector lists AC:L, our assessment raises attack complexity because the MITM prerequisite limits opportunistic mass exploitation. No user interaction or credentials are needed once the MITM position is obtained. No public exploit identified at time of analysis.
Unauthenticated remote attackers can bypass a security feature in Adobe's CAI Content Credentials SDK and gain unauthorized write access, a 7.5-rated integrity flaw confirmed by Adobe PSIRT. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no credentials and no user interaction are required; the practical precondition is that an application embeds the SDK on a network-reachable code path that processes untrusted, externally supplied content. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the medium-to-high severity and the SDK's role in provenance validation make it a priority for integrations that ingest third-party content.
Improper access control in the CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass a security check and gain unauthorized write access, with no user interaction required (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N). The impact is scoped entirely to integrity - the assessed vector shows no confidentiality or availability effect - so practical exposure depends on how much a deploying application trusts Content Credentials data for provenance or security decisions. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; Adobe advisory APSB26-163 is the authoritative source for affected and fixed SDK versions.
Improper access control in the Adobe CAI Content Credentials SDK lets unauthenticated, network-reachable attackers bypass a security check and obtain unauthorized write access to content-credential (provenance) data. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) confirms the flaw needs no credentials and no user interaction, and that impact is confined to integrity - there is no confidentiality or availability effect. The practical exposure hinges on integration: this is an SDK, so reachability and real-world impact depend entirely on whether the host application exposes the affected access-controlled operation to attacker-controlled input; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Improper input validation in the CAI Content Credentials SDK allows a remote, unauthenticated attacker to feed crafted input into the SDK's processing path and bypass its integrity and security checks, resulting in unauthorized write access to Content Credentials data. Adobe PSIRT rates the issue CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), meaning no privileges, no authentication, and no user interaction are required, and the impact is confined to integrity - forged or tampered provenance data - with no direct confidentiality or availability loss. Exposure is the limiting factor: since the SDK is a specialized provenance component, real risk depends on whether a downstream application actually accepts untrusted input through the vulnerable code path; there is no public exploit identified at time of analysis and no evidence of active exploitation.
Path traversal in Adobe's Content Credentials toolkit - spanning the c2patool CLI, the c2pa Rust SDK, and the @contentauth/c2pa-web JavaScript/WASM SDK - enables arbitrary file-system reads outside intended directory boundaries on the local host. Affected versions include c2patool ≤ v0.27.5, c2pa-rs ≤ v0.90.5, and @contentauth/c2pa-web ≤ 0.12.0, with patched releases available for all three. No public exploit has been identified at time of analysis, but the scope-changed flag in the CVSS vector indicates that successful exploitation can reach resources beyond the vulnerable component's own security domain.
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exhaust system resources and cause an application denial-of-service. Three distinct SDK components are affected: the Rust SDK (c2pa), the JavaScript/WebAssembly SDK (@contentauth/c2pa-web), and the command-line tool (c2patool), all across their respective versions prior to the patched releases. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is trivially exploitable without authentication or user interaction.
Null pointer dereference in Adobe's Content Credentials SDKs (Rust SDK ≤c2pa-v0.90.5, JS SDK ≤@contentauth/c2pa-web@0.12.1, CLI tool ≤c2patool-v0.27.5) enables unauthenticated remote attackers to crash any application built on these libraries by supplying a crafted C2PA media payload. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms straightforward remote exploitation with zero prerequisites or user involvement. No active exploitation has been confirmed in CISA KEV and no public exploit code has been identified at time of analysis; vendor-released patches are available for all three SDK components.
Denial-of-service in Adobe's C2PA / Content Credentials SDKs allows a remote attacker to crash any application built on the c2pa Rust SDK (≤0.84.0), the c2patool command-line utility (≤0.16.5), or the @contentauth/c2pa-web JavaScript SDK (≤0.7.0) by supplying malformed input that the library fails to validate. Because exploitation requires no authentication and no user interaction, an application that ingests attacker-controlled assets or manifests can be reliably knocked offline. There is no public exploit identified at time of analysis, and the low EPSS (0.41%) with CISA SSVC exploitation status of 'none' indicates no observed activity yet, though the flaw is assessed as automatable.
Denial-of-service in Adobe's Content Credentials (C2PA) SDK ecosystem lets a remote attacker crash any application that ingests attacker-supplied C2PA-signed assets. The flaw stems from improper input validation (CWE-20) in the Rust c2pa SDK, the @contentauth/c2pa-web JS SDK, and the c2patool command-line utility; exploitation requires no user interaction and no authentication (CVSS 7.5, A:H). No public exploit code has been identified and it is not in CISA KEV, though CISA's SSVC framework flags it as automatable, meaning a working exploit could be scaled easily.
Credential disclosure in Adobe's CAI Content Credentials (C2PA) tooling - spanning the Rust SDK (c2pa ≤0.84.0), the JS SDK (@contentauth/c2pa-web ≤0.7.0), and the c2patool command-line utility (≤0.16.5) - allows a remote attacker to gain unauthorized read access to sensitive credentials due to insufficient protection of stored secrets (CWE-522). The CVSS 3.1 vector (AV:N/PR:N/UI:N, C:H) rates it 7.5 High with no authentication or user interaction required. There is no public exploit identified at time of analysis, CISA SSVC lists exploitation as none, and EPSS is low at 0.39% (31st percentile), so no active exploitation is evidenced.
Server-Side Request Forgery in Adobe's C2PA (Content Credentials) SDK family - the Rust SDK (c2pa), the Node.js web SDK (c2pa-web), and the c2patool CLI - can escalate to arbitrary code execution in the context of the current user. When an application built on these libraries validates a maliciously crafted asset or URL, the SSRF is chained into script injection to hijack the victim's session or account. No public exploit has been identified at time of analysis, and the EPSS score is low (0.18%, 7th percentile), consistent with CISA SSVC rating exploitation as 'none'.
Arbitrary code execution in Adobe's Content Authenticity (CAI) Content Credentials tooling — the c2pa Rust SDK (≤0.84.0), the @contentauth/c2pa-web JS SDK (≤0.7.0), and the c2patool CLI (≤0.16.5) — arises from an untrusted search path (CWE-426) that loads attacker-controlled libraries and runs code as the current user. Adobe PSIRT reports the flaw requires victim interaction (visiting a crafted URL or interacting with a compromised page) and a local attack vector, and there is no public exploit identified at time of analysis. EPSS is low (0.14%, 4th percentile) and CISA SSVC records exploitation as 'none', consistent with a not-yet-exploited but total-technical-impact issue.
Security-control bypass in Adobe's Content Credentials tooling allows remote, unauthenticated attackers to obtain limited unauthorized write access to content handled by affected SDKs by supplying malformed input that the library fails to validate. The issue (CVSS 3.1 score 5.3, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, CWE-20) affects Content Credentials Rust SDK (c2pa) up to c2pa-v0.90.15, C2PA Tool (c2patool) up to v0.27.15, and Content Credentials JS SDK (@contentauth/c2pa-web) up to 0.13.4, and requires only that the target application processes attacker-supplied content or manifests - no authentication, no user interaction, and no non-default configuration are needed. Impact is confined to integrity (I:L) with no confidentiality or availability loss, so the realistic risk is forged or tampered content-provenance records rather than system compromise; no public exploit identified at time of analysis.
Improper input validation in Adobe's Content Credentials SDK (c2patool ≤0.27.15, c2pa Rust SDK ≤0.90.15, and @contentauth/c2pa-web ≤0.13.4) allows unauthenticated remote attackers to bypass security measures and gain limited unauthorized write access when an application processes attacker-controlled Content Credentials manifests or assets. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), no authentication or user interaction is required, but the impact is confined to integrity with no confidentiality or availability loss. No public exploit code or active exploitation has been identified at time of analysis, and the issue is considered a genuine but modest-severity risk rather than a top-tier emergency.
Arbitrary file write via path traversal in Adobe Content Credentials SDK components (the c2patool CLI, the c2pa Rust SDK, and the @contentauth/c2pa-web JavaScript SDK) allows an attacker to write files outside intended directories by supplying a maliciously crafted C2PA asset that a victim extracts. The attack is local (AV:L) and requires user interaction (UI:R)-the victim must actively open or extract the crafted file-while no attacker authentication is required (PR:N). Severity is moderate (CVSS 5.5) with integrity-only impact, and no public exploit identified at time of analysis.
Improper certificate validation in Adobe's CAI Content Credentials (C2PA) tooling lets an attacker slip forged or untrusted provenance data past the certificate/credential validation path, producing a security-feature bypass with integrity impact (CVSS 5.9, CWE-295). Affected implementations are the Content Credentials Rust SDK at or below c2pa-v0.90.15, the JS SDK at or below @contentauth/c2pa-web@0.13.4, and C2PA Tool at or below c2patool-v0.27.15 - any deployment that invokes the affected validation code on attacker-supplied content. Exploitation is unauthenticated (PR:N) and requires no user interaction (UI:N), but is rated AC:H because success depends on conditions beyond the attacker's control, meaning the bypass is not reliably reproducible on demand; no public exploit code has been identified and the issue is not confirmed as actively exploited (CISA KEV).
Improper verification of cryptographic signatures in CAI Content Credentials allows remote, unauthenticated attackers to bypass signature validation and obtain limited write access wherever C2PA manifests are verified against untrusted content. The affected code is the signature-verification path in the c2patool CLI (through v0.27.15), the Rust c2pa SDK (through v0.90.15), and the @contentauth/c2pa-web JS SDK (through v0.13.4). Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) no authentication, no user interaction, and no special configuration are required, but impact is bounded to partial integrity (I:L) with no confidentiality or availability effect, so this is a moderate-severity trust-decision bypass rather than an urgent remote-compromise bug; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Improper input validation in Adobe's CAI Content Credentials tooling (the Rust SDK c2pa-rs, the c2patool CLI, and the @contentauth/c2pa-web JS SDK) lets remote, unauthenticated attackers who supply crafted content manifests bypass a security feature and obtain limited unauthorized write access to content-provenance state. Per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N vector, no credentials or user interaction are required, but the impact is bounded to low-integrity writes with no confidentiality or availability loss, giving this a MEDIUM severity of 5.3. There is no public exploit identified at time of analysis and no KEV listing; the practical exposure is limited to applications and pipelines that actually ingest untrusted content or manifests into the affected component versions.
Improper input validation in Adobe's CAI Content Credentials (C2PA) tooling lets a remote, unauthenticated attacker bypass a security check and obtain unauthorized write access to content-credential data, which can be triggered without any user interaction (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, base 5.9). The affected components are the JavaScript SDK @contentauth/c2pa-web through 0.13.4, the Rust c2pa crate through 0.90.15, and c2patool through 0.27.15. Reliability is deliberately constrained: Adobe states exploitation depends on conditions beyond the attacker's control, reflected as high attack complexity, so this is a moderate-priority integrity/tampering issue rather than a top-tier emergency; no public exploit or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS signal was supplied. Impact is limited to integrity (C:N/A:N) - tampering with provenance/credential data rather than data theft or denial of service.
Improper certificate validation in Adobe's CAI Content Credentials / C2PA tooling lets an attacker bypass trust verification and obtain unauthorized write access to content credentials, an integrity-only impact. Affected components are the JavaScript SDK (@contentauth/c2pa-web 0.13.4 and earlier), the Rust SDK (c2pa 0.90.15 and earlier) and the C2PA command-line tool (c2patool 0.27.15 and earlier); the CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N indicates remote exploitation with no authentication and no user interaction, but a high attack-complexity caveat because success depends on a pre-existing certificate-chain or environmental state the attacker cannot force. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not provided; our independent assessment rates this as a moderate-severity, low-urgency issue confined to integrity.
Improper input validation in Adobe's Content Credentials ecosystem (Rust SDK, JS SDK, and CLI tool) allows local attackers to bypass C2PA content authenticity security controls and gain unauthorized limited write access to credential metadata. Affected are c2pa-v0.90.5 and earlier, @contentauth/c2pa-web@0.12.0 and earlier, and c2patool-v0.27.5 and earlier. No user interaction is required, but the local attack vector (AV:L) and SSVC automation rating of 'no' constrain realistic exploitation to targeted scenarios rather than mass exploitation.
Integer underflow (CWE-191) in Adobe's Content Credentials ecosystem - covering the Rust SDK (c2pa), JavaScript SDK (@contentauth/c2pa-web), and CLI tool (c2patool) - allows a local attacker to crash any application that processes a specially crafted content credential payload, producing a denial-of-service condition. All three components share the underlying parsing logic and are affected up to their respective patch releases. No public exploit or CISA KEV listing has been identified at time of analysis, but the availability of patched versions and a vendor advisory (APSB26-111) confirms vendor-acknowledged impact.
Path traversal in Adobe's CAI Content Credentials ecosystem - spanning the Rust SDK (c2pa-v0.90.5 and earlier), the JavaScript/Web SDK (@contentauth/c2pa-web@0.12.0 and earlier), and the c2patool command-line utility (v0.27.5 and earlier) - enables arbitrary file system reads outside the intended access scope. The flaw is triggered when a victim processes a maliciously crafted file or visits a compromised web page that causes the SDK to resolve attacker-controlled path sequences. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified at time of analysis; patched releases exist for all three components.
Integer overflow in Adobe's CAI Content Credentials SDK family (Rust, JavaScript, and CLI) allows a local attacker to crash the application, producing a denial-of-service condition. All three components - the Rust c2pa crate, the JS c2pa-web package, and the c2patool command-line utility - share the same CWE-190 root cause and are affected up to their respective boundary versions. No public exploit code or active exploitation has been identified; Adobe has released patched versions for all three components per advisory APSB26-111.
Integer overflow in Adobe's Content Credentials ecosystem - spanning the Rust SDK (c2pa ≤ v0.90.5), JavaScript SDK (@contentauth/c2pa-web ≤ 0.12.0), and the c2patool CLI (≤ v0.27.5) - allows denial-of-service through application crash when processing maliciously crafted C2PA assets. The CVSS:3.1/AV:L vector indicates the exploitable surface is file or data ingestion rather than a directly exposed network service, requiring no user interaction or privileges once a crafted asset reaches the parsing pipeline. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Uncontrolled resource consumption in Adobe's CAI Content Credentials ecosystem (c2patool CLI, Rust SDK, and JS SDK) allows a local attacker to trigger application denial-of-service by supplying crafted input that exhausts system resources. Three distinct release artifacts are affected: the c2patool command-line utility, the c2pa Rust crate, and the @contentauth/c2pa-web JavaScript SDK, all patched in a coordinated Adobe PSIRT disclosure (APSB26-111). No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as 'none' with non-automatable attack conditions.
Certificate validation bypass in Adobe's Content Credentials SDK undermines the C2PA provenance chain across three SDK variants - JavaScript/WASM (@contentauth/c2pa-web through 0.12.0), Rust (c2pa through v0.90.5), and CLI (c2patool through v0.27.5) - allowing an attacker-controlled certificate to be accepted as legitimate when a victim visits a malicious URL or interacts with a compromised web page. Successful exploitation grants unauthorized write access to content credentials, enabling an attacker to forge provenance metadata and defeat the product's core integrity guarantee. No public exploit has been identified at time of analysis; vendor-released patches exist for all three affected SDK variants.
Improper input validation across Adobe's Content Credentials JS SDK, Rust SDK, and command-line tool allows a remote unauthenticated attacker to bypass integrity verification and gain unauthorized write access to C2PA-signed content metadata. All three SDK components prior to their respective patch releases are affected, and exploitation requires a victim to visit a maliciously crafted URL or interact with a compromised web page. No public exploit code or active exploitation has been identified at time of analysis, though the write-impact on content authenticity signals carries meaningful trust implications for downstream consumers.
Integer underflow in Adobe's Content Credentials SDK crashes any application that parses a specially crafted C2PA manifest file, producing a denial-of-service condition. The Rust crate (c2pa ≤0.90.5), JavaScript/WASM package (@contentauth/c2pa-web ≤0.12.0), and CLI tool (c2patool ≤0.27.5) are all affected, with patched releases confirmed by Adobe advisory APSB26-111. No public exploit code and no CISA KEV listing have been identified at time of analysis; real-world impact is highest in automated media ingestion pipelines that validate C2PA provenance on user-supplied files.
Uncontrolled resource consumption in Adobe's Content Credentials ecosystem - spanning the c2patool CLI (≤v0.27.5), Rust SDK c2pa (≤v0.90.5), and JavaScript SDK @contentauth/c2pa-web (≤v0.12.0) - allows a local attacker without elevated privileges to exhaust system resources and cause an application denial-of-service. The vulnerability does not require user interaction, lowering the bar for exploitation in automated pipelines. Adobe has released patches across all three components via advisory APSB26-111, and no public exploit code or active exploitation has been identified at time of analysis.
Integer overflow in Adobe's Content Credentials SDK and CLI toolchain crashes the application when processing crafted input, resulting in a denial-of-service condition. Affected components span the Rust SDK (c2pa), the command-line tool (c2patool), and the JavaScript/WebAssembly SDK (@contentauth/c2pa-web), all at versions prior to their respective patch releases. No public exploit has been identified at time of analysis, and SSVC assesses exploitation as none with non-automatable delivery.
SSRF with privilege escalation affects Adobe's Content Credentials SDK and CLI toolchain, enabling a network-based attacker to induce the victim's client to issue server-side requests to unintended internal or external targets. Exploitation requires user interaction - a victim must visit a crafted URL or engage with a compromised web page - but the CVSS scope change (S:C) indicates the vulnerability can reach beyond the directly vulnerable component to affect other systems or services. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Uncontrolled resource consumption in Adobe's C2PA Content Credentials Rust SDK, CLI tool (c2patool), and JavaScript web SDK allows a local attacker supplying a crafted input to exhaust system resources and crash the application. All three library families are affected across distinct runtimes - Rust, Node.js, and native binary - with patched releases available for each. No public exploit exists, SSVC classifies exploitation as none, and EPSS sits at the 5th percentile, indicating low real-world exploitation pressure despite the zero-user-interaction requirement.
Integer overflow in Adobe's Content Credentials SDK family (c2pa Rust SDK, c2pa-web JS SDK, and c2patool CLI) allows a local attacker to crash any application that processes a specially crafted C2PA manifest, resulting in denial of service. All three components share the vulnerable parsing logic and are affected across versions up to c2pa-v0.84.0, @contentauth/c2pa-web@0.7.0, and c2patool-v0.16.5 respectively. No public exploit exists and SSVC confirms no observed exploitation; however, patches are available and should be applied given the zero-privilege-required local trigger condition.
Arbitrary file system read in Adobe's Content Credentials ecosystem (C2PA Rust SDK, JS SDK, and c2patool CLI) allows an attacker who crafts a malicious C2PA-signed file to access files and directories outside the intended scope when a victim opens that file. The root cause is improper input validation (CWE-20), likely path traversal in manifest or asset reference parsing. No public exploit code exists at time of analysis, EPSS is 0.15% (5th percentile), and CISA SSVC rates exploitation as none - real-world risk is currently contained but the confidentiality impact is rated High given successful arbitrary file read.
Security feature bypass in Adobe's Content Credentials (C2PA) SDKs - the Rust SDK (≤0.84.0), JavaScript SDK (≤0.7.0), and CLI tool (≤0.16.5) - allows unauthorized write access to content provenance data through improper input validation (CWE-20). No active exploitation is confirmed: SSVC rates exploitation as none, the vulnerability is absent from CISA KEV, and EPSS sits at 0.16% (6th percentile), signaling low real-world threat pressure at this time. Adobe has released patches across all three components under advisory APSB26-80.
Improper input validation in Adobe's Content Credentials suite (C2PA Rust SDK, JS SDK, and c2patool CLI) allows a local attacker without privileges to crash the application by supplying malformed C2PA manifest content, resulting in a denial-of-service condition. Affected components span the Rust library (c2pa ≤ 0.84.0), the Node.js web SDK (@contentauth/c2pa-web ≤ 0.7.0), and the command-line tool (c2patool ≤ v0.16.5). No public exploit has been identified at time of analysis, and CISA SSVC rates exploitation status as none with non-automatable attack paths.
Integer underflow (CWE-191) in Adobe's Content Credentials ecosystem - spanning the Rust SDK (c2pa), JavaScript/Node.js SDK (c2pa-web), and c2patool command-line utility - crashes the application when processing a maliciously crafted C2PA manifest or media file, resulting in a denial-of-service condition. All three components share the same vulnerable code path, broadening the attack surface across toolchains. No public exploit has been identified at time of analysis; EPSS at 0.15% (5th percentile) and SSVC exploitation status of 'none' confirm this is not currently being targeted.
Integer underflow in Adobe's C2PA Content Credentials SDKs (Rust, JavaScript/Node.js, and CLI tool) allows an attacker to crash the host application by supplying a maliciously crafted C2PA manifest, resulting in a denial-of-service condition. All three release tracks are affected - the Rust SDK (≤0.84.0), the JS SDK (≤0.7.0), and c2patool (≤0.16.5) - with vendor-released patches available for each. No public exploit code has been identified at time of analysis, and EPSS sits at the 5th percentile, consistent with SSVC's 'exploitation: none' assessment.
Server-side request forgery in Adobe Content Credentials (CAI Content Credentials SDK) allows unauthenticated remote attackers to induce the server to make arbitrary outbound requests, potentially reaching internal services and escalating privileges. The CVSS 3.1 base score is 8.6 (HIGH) with a changed scope, high confidentiality impact, and no integrity or availability impact. Exploitation requires no user interaction; no public exploit code has been identified at time of analysis, and the vendor advisory APSB26-163 should be consulted for fixes.
A signature-verification bypass in the CAI Content Credentials SDK allows an unauthenticated, network-reachable attacker to submit content or a token bearing a forged or tampered cryptographic signature that the SDK's verifier accepts, yielding unauthorized write access to systems that rely on that verification as a trust decision. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) the attack needs no credentials and no user interaction, and the assessment confines impact to integrity only, with no confidentiality or availability loss. The practical exposure is narrow but real: only deployments that actually consume the SDK to validate signatures or claims as a security control are affected, and no public exploit code was identified at time of analysis, so this is a genuine integrity issue rather than an acute emergency.
Improper verification of cryptographic signatures in the CAI Content Credentials SDK allows unauthenticated remote attackers to supply forged or improperly signed content credentials that the SDK accepts as authentic, bypassing the security check and gaining unauthorized write access to whatever the SDK's verification verdict gates. The CVSS 3.1 base score is 7.5 (High) under the vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - an integrity-only signature-verification bypass (CWE-347) with no confidentiality or availability impact, requiring no authentication and no user interaction. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; real-world risk is highest in deployments that make publishing, authorization, or authenticity decisions solely on the SDK's verification result, and negligible where that result is not treated as a trust boundary.
Denial of service in Adobe's CAI (Content Authenticity Initiative) Content Credentials SDK stems from uncontrolled resource consumption when the library parses attacker-supplied assets or their embedded Content Credentials / C2PA manifest data. The vulnerable path is network-reachable with low attack complexity and, per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requires no authentication and no user interaction, yielding a 7.5 base score with availability-only impact; confidentiality and integrity are unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied, so practical risk is bounded by exposure: because this is an embedded SDK rather than a standalone service, only integrations that feed untrusted, externally sourced content into the parsing/verification path are realistically reachable, while deployments processing only trusted or internally generated assets are not.
Denial-of-service in the CAI Content Credentials SDK allows remote unauthenticated attackers to exhaust system resources by supplying crafted Content Credentials data to an application that parses or verifies it. The issue is availability-only (CVSS 3.1 7.5, CWE-400) with no confidentiality or integrity impact, and no public exploit has been identified at time of analysis. Deployments that do not expose SDK-backed parsing to untrusted input face substantially lower real-world risk.
Improper input validation in Adobe's CAI Content Credentials SDK (advisory APSB26-163) lets remote attackers bypass a security feature and obtain unauthorized write access, effectively allowing modification or forgery of protected content-credential data. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) means the flaw is network-reachable, low complexity, unauthenticated, and requires no user interaction, so any application or service that embeds the SDK and exposes its input-processing path to untrusted input is in scope. Impact is confined to integrity (I:H) with no confidentiality or availability loss, and no public exploit code or CISA KEV entry was identified at time of analysis.
Improper verification of cryptographic signatures in Adobe's CAI Content Credentials SDK allows remote, unauthenticated attackers to submit a forged or tampered Content Credentials manifest that the SDK accepts as valid, bypassing a security feature and granting unauthorized write access to credential data (CWE-347; CVSS 3.1 7.5). Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, no credentials and no user interaction are required, and the impact is integrity-only, with confidentiality and availability unaffected; in practice exploitation depends on the vulnerable SDK version being deployed and the consuming application treating signature verification as a trust boundary. This is a moderate-priority integrity issue rather than a top-tier emergency, and no public exploit code or confirmed active exploitation was identified in the available intelligence at time of analysis.
Signature-verification bypass in Adobe Content Credentials SDK allows unauthenticated, network-based attackers to forge or tamper with signed content credentials, bypassing integrity checks to gain unauthorized write access. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) indicates a low-complexity flaw with no user interaction and a pure integrity impact. No public exploit code has been identified at time of analysis, but risk is elevated for applications that rely on the SDK's verification result as a trust or authorization decision. Confirm vulnerable SDK versions against Adobe APSB26-163.
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.
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.
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.
Integer overflow (CWE-190) in the CAI Content Credentials SDK lets unauthenticated remote attackers crash applications that parse externally supplied media or embedded Content Credentials manifests, producing a denial-of-service condition. Affected deployments are those that invoke the SDK against untrusted input - for example services that automatically ingest and verify uploaded or fetched media - while systems that only process trusted, internally generated assets are far less exposed. The vulnerability is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requires no user interaction, causes availability loss only (no disclosure or modification), and no public exploit code has been identified at time of analysis; the vendor advisory is Adobe APSB26-163.
Improper input validation in the Adobe CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass a security control and obtain unauthorized write access. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, any deployment that exposes the vulnerable SDK input path to attacker-supplied content credentials data is reachable without credentials or user interaction, and the impact is integrity-only (C:N/I:H/A:N), meaning tampering with data rather than disclosure or denial of service. Rated CVSS 7.5 (High) and reported directly by Adobe PSIRT via advisory APSB26-163; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Improper input validation in the CAI Content Credentials SDK (Adobe security bulletin APSB26-163) lets unauthenticated remote attackers bypass the SDK's content-credential validation path and gain unauthorized write access, yielding an integrity-only impact (C:N/I:H/A:N, CVSS 7.5). Any deployment that ingests attacker-supplied or externally sourced credential data and runs the vulnerable SDK version through its parse/verify routine is exposed; no authentication (PR:N) and no user interaction (UI:N) are required per the assessed vector, so a default-configured verification service reachable from the network is sufficient. The practical limiting factor is deployment scope rather than a configuration toggle - the flaw only matters where untrusted content actually flows into the SDK - and there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) at the time of writing, which keeps this an elevated but not top-tier priority.
Improper certificate validation in the CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass security features and gain unauthorized write access (CVSS 7.5, High). Exploitation requires the attacker to present a forged or untrusted certificate that the SDK incorrectly accepts, and no user interaction is needed. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Improper certificate validation in Adobe's CAI Content Credentials SDK (Content Credentials SDK) allows remote, unauthenticated attackers to bypass certificate trust checks and gain unauthorized write access, effectively letting them forge or tamper with signed Content Credentials data with no user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5). Impact is bounded to integrity - no confidentiality or availability effect - and only deployments that actually invoke the SDK to validate Content Credentials certificates are exposed. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; exploitation in practice requires the attacker to supply crafted signed content or hold a man-in-the-middle position on the certificate validation path.
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.
Improper input validation in the CAI Content Credentials SDK lets remote, unauthenticated attackers bypass the SDK's security control and obtain unauthorized write access to content-credential data, per Adobe advisory APSB26-163. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) indicates a network-reachable, low-complexity flaw requiring no authentication and no user interaction, with impact confined to integrity - confidentiality and availability are unaffected. Only applications that embed a vulnerable version of the SDK and expose its input-processing/validation path to network-supplied content are affected, and no public exploit code was identified at time of analysis.
Improper input validation in the Adobe CAI Content Credentials SDK lets remote attackers bypass a security feature and gain unauthorized write access to content-credential processing. The flaw is network-reachable, low-complexity, requires no authentication (PR:N) and no user interaction (UI:N), yielding a CVSS 3.1 score of 7.5, but the scored impact is integrity-only (C:N/I:H/A:N) rather than code execution or data disclosure. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; exploitation is contingent on a deployed application embedding the SDK and exposing its C2PA manifest parsing/validation path to attacker-supplied input.
Improper certificate validation in the CAI Content Credentials SDK enables a network-positioned attacker who can intercept TLS connections to bypass security features and gain unauthorized write access. Exploitation requires a man-in-the-middle (MITM) position to supply a forged or invalid certificate that the SDK accepts; the assessed CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, and although the input CVSS 7.5 vector lists AC:L, our assessment raises attack complexity because the MITM prerequisite limits opportunistic mass exploitation. No user interaction or credentials are needed once the MITM position is obtained. No public exploit identified at time of analysis.
Unauthenticated remote attackers can bypass a security feature in Adobe's CAI Content Credentials SDK and gain unauthorized write access, a 7.5-rated integrity flaw confirmed by Adobe PSIRT. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no credentials and no user interaction are required; the practical precondition is that an application embeds the SDK on a network-reachable code path that processes untrusted, externally supplied content. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the medium-to-high severity and the SDK's role in provenance validation make it a priority for integrations that ingest third-party content.
Improper access control in the CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass a security check and gain unauthorized write access, with no user interaction required (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N). The impact is scoped entirely to integrity - the assessed vector shows no confidentiality or availability effect - so practical exposure depends on how much a deploying application trusts Content Credentials data for provenance or security decisions. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; Adobe advisory APSB26-163 is the authoritative source for affected and fixed SDK versions.
Improper access control in the Adobe CAI Content Credentials SDK lets unauthenticated, network-reachable attackers bypass a security check and obtain unauthorized write access to content-credential (provenance) data. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) confirms the flaw needs no credentials and no user interaction, and that impact is confined to integrity - there is no confidentiality or availability effect. The practical exposure hinges on integration: this is an SDK, so reachability and real-world impact depend entirely on whether the host application exposes the affected access-controlled operation to attacker-controlled input; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Improper input validation in the CAI Content Credentials SDK allows a remote, unauthenticated attacker to feed crafted input into the SDK's processing path and bypass its integrity and security checks, resulting in unauthorized write access to Content Credentials data. Adobe PSIRT rates the issue CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), meaning no privileges, no authentication, and no user interaction are required, and the impact is confined to integrity - forged or tampered provenance data - with no direct confidentiality or availability loss. Exposure is the limiting factor: since the SDK is a specialized provenance component, real risk depends on whether a downstream application actually accepts untrusted input through the vulnerable code path; there is no public exploit identified at time of analysis and no evidence of active exploitation.
Path traversal in Adobe's Content Credentials toolkit - spanning the c2patool CLI, the c2pa Rust SDK, and the @contentauth/c2pa-web JavaScript/WASM SDK - enables arbitrary file-system reads outside intended directory boundaries on the local host. Affected versions include c2patool ≤ v0.27.5, c2pa-rs ≤ v0.90.5, and @contentauth/c2pa-web ≤ 0.12.0, with patched releases available for all three. No public exploit has been identified at time of analysis, but the scope-changed flag in the CVSS vector indicates that successful exploitation can reach resources beyond the vulnerable component's own security domain.
Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exhaust system resources and cause an application denial-of-service. Three distinct SDK components are affected: the Rust SDK (c2pa), the JavaScript/WebAssembly SDK (@contentauth/c2pa-web), and the command-line tool (c2patool), all across their respective versions prior to the patched releases. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is trivially exploitable without authentication or user interaction.
Null pointer dereference in Adobe's Content Credentials SDKs (Rust SDK ≤c2pa-v0.90.5, JS SDK ≤@contentauth/c2pa-web@0.12.1, CLI tool ≤c2patool-v0.27.5) enables unauthenticated remote attackers to crash any application built on these libraries by supplying a crafted C2PA media payload. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms straightforward remote exploitation with zero prerequisites or user involvement. No active exploitation has been confirmed in CISA KEV and no public exploit code has been identified at time of analysis; vendor-released patches are available for all three SDK components.
Denial-of-service in Adobe's C2PA / Content Credentials SDKs allows a remote attacker to crash any application built on the c2pa Rust SDK (≤0.84.0), the c2patool command-line utility (≤0.16.5), or the @contentauth/c2pa-web JavaScript SDK (≤0.7.0) by supplying malformed input that the library fails to validate. Because exploitation requires no authentication and no user interaction, an application that ingests attacker-controlled assets or manifests can be reliably knocked offline. There is no public exploit identified at time of analysis, and the low EPSS (0.41%) with CISA SSVC exploitation status of 'none' indicates no observed activity yet, though the flaw is assessed as automatable.
Denial-of-service in Adobe's Content Credentials (C2PA) SDK ecosystem lets a remote attacker crash any application that ingests attacker-supplied C2PA-signed assets. The flaw stems from improper input validation (CWE-20) in the Rust c2pa SDK, the @contentauth/c2pa-web JS SDK, and the c2patool command-line utility; exploitation requires no user interaction and no authentication (CVSS 7.5, A:H). No public exploit code has been identified and it is not in CISA KEV, though CISA's SSVC framework flags it as automatable, meaning a working exploit could be scaled easily.
Credential disclosure in Adobe's CAI Content Credentials (C2PA) tooling - spanning the Rust SDK (c2pa ≤0.84.0), the JS SDK (@contentauth/c2pa-web ≤0.7.0), and the c2patool command-line utility (≤0.16.5) - allows a remote attacker to gain unauthorized read access to sensitive credentials due to insufficient protection of stored secrets (CWE-522). The CVSS 3.1 vector (AV:N/PR:N/UI:N, C:H) rates it 7.5 High with no authentication or user interaction required. There is no public exploit identified at time of analysis, CISA SSVC lists exploitation as none, and EPSS is low at 0.39% (31st percentile), so no active exploitation is evidenced.
Server-Side Request Forgery in Adobe's C2PA (Content Credentials) SDK family - the Rust SDK (c2pa), the Node.js web SDK (c2pa-web), and the c2patool CLI - can escalate to arbitrary code execution in the context of the current user. When an application built on these libraries validates a maliciously crafted asset or URL, the SSRF is chained into script injection to hijack the victim's session or account. No public exploit has been identified at time of analysis, and the EPSS score is low (0.18%, 7th percentile), consistent with CISA SSVC rating exploitation as 'none'.
Arbitrary code execution in Adobe's Content Authenticity (CAI) Content Credentials tooling — the c2pa Rust SDK (≤0.84.0), the @contentauth/c2pa-web JS SDK (≤0.7.0), and the c2patool CLI (≤0.16.5) — arises from an untrusted search path (CWE-426) that loads attacker-controlled libraries and runs code as the current user. Adobe PSIRT reports the flaw requires victim interaction (visiting a crafted URL or interacting with a compromised page) and a local attack vector, and there is no public exploit identified at time of analysis. EPSS is low (0.14%, 4th percentile) and CISA SSVC records exploitation as 'none', consistent with a not-yet-exploited but total-technical-impact issue.
Security-control bypass in Adobe's Content Credentials tooling allows remote, unauthenticated attackers to obtain limited unauthorized write access to content handled by affected SDKs by supplying malformed input that the library fails to validate. The issue (CVSS 3.1 score 5.3, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, CWE-20) affects Content Credentials Rust SDK (c2pa) up to c2pa-v0.90.15, C2PA Tool (c2patool) up to v0.27.15, and Content Credentials JS SDK (@contentauth/c2pa-web) up to 0.13.4, and requires only that the target application processes attacker-supplied content or manifests - no authentication, no user interaction, and no non-default configuration are needed. Impact is confined to integrity (I:L) with no confidentiality or availability loss, so the realistic risk is forged or tampered content-provenance records rather than system compromise; no public exploit identified at time of analysis.
Improper input validation in Adobe's Content Credentials SDK (c2patool ≤0.27.15, c2pa Rust SDK ≤0.90.15, and @contentauth/c2pa-web ≤0.13.4) allows unauthenticated remote attackers to bypass security measures and gain limited unauthorized write access when an application processes attacker-controlled Content Credentials manifests or assets. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), no authentication or user interaction is required, but the impact is confined to integrity with no confidentiality or availability loss. No public exploit code or active exploitation has been identified at time of analysis, and the issue is considered a genuine but modest-severity risk rather than a top-tier emergency.
Arbitrary file write via path traversal in Adobe Content Credentials SDK components (the c2patool CLI, the c2pa Rust SDK, and the @contentauth/c2pa-web JavaScript SDK) allows an attacker to write files outside intended directories by supplying a maliciously crafted C2PA asset that a victim extracts. The attack is local (AV:L) and requires user interaction (UI:R)-the victim must actively open or extract the crafted file-while no attacker authentication is required (PR:N). Severity is moderate (CVSS 5.5) with integrity-only impact, and no public exploit identified at time of analysis.
Improper certificate validation in Adobe's CAI Content Credentials (C2PA) tooling lets an attacker slip forged or untrusted provenance data past the certificate/credential validation path, producing a security-feature bypass with integrity impact (CVSS 5.9, CWE-295). Affected implementations are the Content Credentials Rust SDK at or below c2pa-v0.90.15, the JS SDK at or below @contentauth/c2pa-web@0.13.4, and C2PA Tool at or below c2patool-v0.27.15 - any deployment that invokes the affected validation code on attacker-supplied content. Exploitation is unauthenticated (PR:N) and requires no user interaction (UI:N), but is rated AC:H because success depends on conditions beyond the attacker's control, meaning the bypass is not reliably reproducible on demand; no public exploit code has been identified and the issue is not confirmed as actively exploited (CISA KEV).
Improper verification of cryptographic signatures in CAI Content Credentials allows remote, unauthenticated attackers to bypass signature validation and obtain limited write access wherever C2PA manifests are verified against untrusted content. The affected code is the signature-verification path in the c2patool CLI (through v0.27.15), the Rust c2pa SDK (through v0.90.15), and the @contentauth/c2pa-web JS SDK (through v0.13.4). Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) no authentication, no user interaction, and no special configuration are required, but impact is bounded to partial integrity (I:L) with no confidentiality or availability effect, so this is a moderate-severity trust-decision bypass rather than an urgent remote-compromise bug; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Improper input validation in Adobe's CAI Content Credentials tooling (the Rust SDK c2pa-rs, the c2patool CLI, and the @contentauth/c2pa-web JS SDK) lets remote, unauthenticated attackers who supply crafted content manifests bypass a security feature and obtain limited unauthorized write access to content-provenance state. Per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N vector, no credentials or user interaction are required, but the impact is bounded to low-integrity writes with no confidentiality or availability loss, giving this a MEDIUM severity of 5.3. There is no public exploit identified at time of analysis and no KEV listing; the practical exposure is limited to applications and pipelines that actually ingest untrusted content or manifests into the affected component versions.
Improper input validation in Adobe's CAI Content Credentials (C2PA) tooling lets a remote, unauthenticated attacker bypass a security check and obtain unauthorized write access to content-credential data, which can be triggered without any user interaction (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, base 5.9). The affected components are the JavaScript SDK @contentauth/c2pa-web through 0.13.4, the Rust c2pa crate through 0.90.15, and c2patool through 0.27.15. Reliability is deliberately constrained: Adobe states exploitation depends on conditions beyond the attacker's control, reflected as high attack complexity, so this is a moderate-priority integrity/tampering issue rather than a top-tier emergency; no public exploit or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS signal was supplied. Impact is limited to integrity (C:N/A:N) - tampering with provenance/credential data rather than data theft or denial of service.
Improper certificate validation in Adobe's CAI Content Credentials / C2PA tooling lets an attacker bypass trust verification and obtain unauthorized write access to content credentials, an integrity-only impact. Affected components are the JavaScript SDK (@contentauth/c2pa-web 0.13.4 and earlier), the Rust SDK (c2pa 0.90.15 and earlier) and the C2PA command-line tool (c2patool 0.27.15 and earlier); the CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N indicates remote exploitation with no authentication and no user interaction, but a high attack-complexity caveat because success depends on a pre-existing certificate-chain or environmental state the attacker cannot force. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not provided; our independent assessment rates this as a moderate-severity, low-urgency issue confined to integrity.
Improper input validation in Adobe's Content Credentials ecosystem (Rust SDK, JS SDK, and CLI tool) allows local attackers to bypass C2PA content authenticity security controls and gain unauthorized limited write access to credential metadata. Affected are c2pa-v0.90.5 and earlier, @contentauth/c2pa-web@0.12.0 and earlier, and c2patool-v0.27.5 and earlier. No user interaction is required, but the local attack vector (AV:L) and SSVC automation rating of 'no' constrain realistic exploitation to targeted scenarios rather than mass exploitation.
Integer underflow (CWE-191) in Adobe's Content Credentials ecosystem - covering the Rust SDK (c2pa), JavaScript SDK (@contentauth/c2pa-web), and CLI tool (c2patool) - allows a local attacker to crash any application that processes a specially crafted content credential payload, producing a denial-of-service condition. All three components share the underlying parsing logic and are affected up to their respective patch releases. No public exploit or CISA KEV listing has been identified at time of analysis, but the availability of patched versions and a vendor advisory (APSB26-111) confirms vendor-acknowledged impact.
Path traversal in Adobe's CAI Content Credentials ecosystem - spanning the Rust SDK (c2pa-v0.90.5 and earlier), the JavaScript/Web SDK (@contentauth/c2pa-web@0.12.0 and earlier), and the c2patool command-line utility (v0.27.5 and earlier) - enables arbitrary file system reads outside the intended access scope. The flaw is triggered when a victim processes a maliciously crafted file or visits a compromised web page that causes the SDK to resolve attacker-controlled path sequences. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified at time of analysis; patched releases exist for all three components.
Integer overflow in Adobe's CAI Content Credentials SDK family (Rust, JavaScript, and CLI) allows a local attacker to crash the application, producing a denial-of-service condition. All three components - the Rust c2pa crate, the JS c2pa-web package, and the c2patool command-line utility - share the same CWE-190 root cause and are affected up to their respective boundary versions. No public exploit code or active exploitation has been identified; Adobe has released patched versions for all three components per advisory APSB26-111.
Integer overflow in Adobe's Content Credentials ecosystem - spanning the Rust SDK (c2pa ≤ v0.90.5), JavaScript SDK (@contentauth/c2pa-web ≤ 0.12.0), and the c2patool CLI (≤ v0.27.5) - allows denial-of-service through application crash when processing maliciously crafted C2PA assets. The CVSS:3.1/AV:L vector indicates the exploitable surface is file or data ingestion rather than a directly exposed network service, requiring no user interaction or privileges once a crafted asset reaches the parsing pipeline. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Uncontrolled resource consumption in Adobe's CAI Content Credentials ecosystem (c2patool CLI, Rust SDK, and JS SDK) allows a local attacker to trigger application denial-of-service by supplying crafted input that exhausts system resources. Three distinct release artifacts are affected: the c2patool command-line utility, the c2pa Rust crate, and the @contentauth/c2pa-web JavaScript SDK, all patched in a coordinated Adobe PSIRT disclosure (APSB26-111). No public exploit code has been identified at time of analysis, and CISA SSVC rates exploitation as 'none' with non-automatable attack conditions.
Certificate validation bypass in Adobe's Content Credentials SDK undermines the C2PA provenance chain across three SDK variants - JavaScript/WASM (@contentauth/c2pa-web through 0.12.0), Rust (c2pa through v0.90.5), and CLI (c2patool through v0.27.5) - allowing an attacker-controlled certificate to be accepted as legitimate when a victim visits a malicious URL or interacts with a compromised web page. Successful exploitation grants unauthorized write access to content credentials, enabling an attacker to forge provenance metadata and defeat the product's core integrity guarantee. No public exploit has been identified at time of analysis; vendor-released patches exist for all three affected SDK variants.
Improper input validation across Adobe's Content Credentials JS SDK, Rust SDK, and command-line tool allows a remote unauthenticated attacker to bypass integrity verification and gain unauthorized write access to C2PA-signed content metadata. All three SDK components prior to their respective patch releases are affected, and exploitation requires a victim to visit a maliciously crafted URL or interact with a compromised web page. No public exploit code or active exploitation has been identified at time of analysis, though the write-impact on content authenticity signals carries meaningful trust implications for downstream consumers.
Integer underflow in Adobe's Content Credentials SDK crashes any application that parses a specially crafted C2PA manifest file, producing a denial-of-service condition. The Rust crate (c2pa ≤0.90.5), JavaScript/WASM package (@contentauth/c2pa-web ≤0.12.0), and CLI tool (c2patool ≤0.27.5) are all affected, with patched releases confirmed by Adobe advisory APSB26-111. No public exploit code and no CISA KEV listing have been identified at time of analysis; real-world impact is highest in automated media ingestion pipelines that validate C2PA provenance on user-supplied files.
Uncontrolled resource consumption in Adobe's Content Credentials ecosystem - spanning the c2patool CLI (≤v0.27.5), Rust SDK c2pa (≤v0.90.5), and JavaScript SDK @contentauth/c2pa-web (≤v0.12.0) - allows a local attacker without elevated privileges to exhaust system resources and cause an application denial-of-service. The vulnerability does not require user interaction, lowering the bar for exploitation in automated pipelines. Adobe has released patches across all three components via advisory APSB26-111, and no public exploit code or active exploitation has been identified at time of analysis.
Integer overflow in Adobe's Content Credentials SDK and CLI toolchain crashes the application when processing crafted input, resulting in a denial-of-service condition. Affected components span the Rust SDK (c2pa), the command-line tool (c2patool), and the JavaScript/WebAssembly SDK (@contentauth/c2pa-web), all at versions prior to their respective patch releases. No public exploit has been identified at time of analysis, and SSVC assesses exploitation as none with non-automatable delivery.
SSRF with privilege escalation affects Adobe's Content Credentials SDK and CLI toolchain, enabling a network-based attacker to induce the victim's client to issue server-side requests to unintended internal or external targets. Exploitation requires user interaction - a victim must visit a crafted URL or engage with a compromised web page - but the CVSS scope change (S:C) indicates the vulnerability can reach beyond the directly vulnerable component to affect other systems or services. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Uncontrolled resource consumption in Adobe's C2PA Content Credentials Rust SDK, CLI tool (c2patool), and JavaScript web SDK allows a local attacker supplying a crafted input to exhaust system resources and crash the application. All three library families are affected across distinct runtimes - Rust, Node.js, and native binary - with patched releases available for each. No public exploit exists, SSVC classifies exploitation as none, and EPSS sits at the 5th percentile, indicating low real-world exploitation pressure despite the zero-user-interaction requirement.
Integer overflow in Adobe's Content Credentials SDK family (c2pa Rust SDK, c2pa-web JS SDK, and c2patool CLI) allows a local attacker to crash any application that processes a specially crafted C2PA manifest, resulting in denial of service. All three components share the vulnerable parsing logic and are affected across versions up to c2pa-v0.84.0, @contentauth/c2pa-web@0.7.0, and c2patool-v0.16.5 respectively. No public exploit exists and SSVC confirms no observed exploitation; however, patches are available and should be applied given the zero-privilege-required local trigger condition.
Arbitrary file system read in Adobe's Content Credentials ecosystem (C2PA Rust SDK, JS SDK, and c2patool CLI) allows an attacker who crafts a malicious C2PA-signed file to access files and directories outside the intended scope when a victim opens that file. The root cause is improper input validation (CWE-20), likely path traversal in manifest or asset reference parsing. No public exploit code exists at time of analysis, EPSS is 0.15% (5th percentile), and CISA SSVC rates exploitation as none - real-world risk is currently contained but the confidentiality impact is rated High given successful arbitrary file read.
Security feature bypass in Adobe's Content Credentials (C2PA) SDKs - the Rust SDK (≤0.84.0), JavaScript SDK (≤0.7.0), and CLI tool (≤0.16.5) - allows unauthorized write access to content provenance data through improper input validation (CWE-20). No active exploitation is confirmed: SSVC rates exploitation as none, the vulnerability is absent from CISA KEV, and EPSS sits at 0.16% (6th percentile), signaling low real-world threat pressure at this time. Adobe has released patches across all three components under advisory APSB26-80.
Improper input validation in Adobe's Content Credentials suite (C2PA Rust SDK, JS SDK, and c2patool CLI) allows a local attacker without privileges to crash the application by supplying malformed C2PA manifest content, resulting in a denial-of-service condition. Affected components span the Rust library (c2pa ≤ 0.84.0), the Node.js web SDK (@contentauth/c2pa-web ≤ 0.7.0), and the command-line tool (c2patool ≤ v0.16.5). No public exploit has been identified at time of analysis, and CISA SSVC rates exploitation status as none with non-automatable attack paths.
Integer underflow (CWE-191) in Adobe's Content Credentials ecosystem - spanning the Rust SDK (c2pa), JavaScript/Node.js SDK (c2pa-web), and c2patool command-line utility - crashes the application when processing a maliciously crafted C2PA manifest or media file, resulting in a denial-of-service condition. All three components share the same vulnerable code path, broadening the attack surface across toolchains. No public exploit has been identified at time of analysis; EPSS at 0.15% (5th percentile) and SSVC exploitation status of 'none' confirm this is not currently being targeted.
Integer underflow in Adobe's C2PA Content Credentials SDKs (Rust, JavaScript/Node.js, and CLI tool) allows an attacker to crash the host application by supplying a maliciously crafted C2PA manifest, resulting in a denial-of-service condition. All three release tracks are affected - the Rust SDK (≤0.84.0), the JS SDK (≤0.7.0), and c2patool (≤0.16.5) - with vendor-released patches available for each. No public exploit code has been identified at time of analysis, and EPSS sits at the 5th percentile, consistent with SSVC's 'exploitation: none' assessment.