Skip to main content

Content Credentials CVE-2026-48290

| EUVDEUVD-2026-44527 HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2026-07-14 psirt@adobe.com GHSA-5j74-v2xh-7cpv
8.2
CVSS 3.1 · Vendor: adobe
Share

Severity by source

Vendor (adobe) PRIMARY
8.2 HIGH
AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
vuln.today AI
8.2 HIGH

Local processing of attacker-supplied content with required user interaction (AV:L, UI:R, PR:N); scope changes into the user session (S:C) with high confidentiality and integrity impact and no availability effect.

3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Analysis Generated
Jul 22, 2026 - 11:33 vuln.today
CVE Published
Jul 14, 2026 - 22:17 nvd
HIGH 8.2

DescriptionCVE.org

CAI Content Credentials is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to inject malicious scripts into a web page, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page. Scope is changed.

AnalysisAI

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'.

Technical ContextAI

C2PA (Coalition for Content Provenance and Authenticity) is the open standard implemented by Adobe's Content Credentials tooling to embed and verify cryptographically signed provenance manifests inside media files. The affected components are the Rust reference SDK (cpe:2.3:a:adobe:c2pa, rust), the JavaScript/Node.js binding c2pa-web (cpe:2.3:a:adobe:c2pa-web, node.js), and the c2patool command-line utility (cpe:2.3:a:adobe:c2patool). The root cause is CWE-918 (Server-Side Request Forgery): when the manifest/validation logic resolves an attacker-controlled reference (for example a remote manifest or ingredient URL) it issues an outbound request without adequate validation, which per the advisory can be chained into script injection and code execution in the current user's context. The CVSS vector's AV:L with S:C indicates the untrusted fetch/processing occurs in a locally invoked verification workflow but crosses a security boundary (scope change) into the user's session or host.

RemediationAI

Vendor-released patches are available - upgrade the Rust SDK to c2pa-v0.85.2, the Node.js web SDK to @contentauth/c2pa-web@0.9.0, and the command-line tool to c2patool-v0.26.65, per Adobe advisory APSB26-80 (https://helpx.adobe.com/security/products/content-authenticity-sdk/apsb26-80.html). Because these are libraries, also rebuild and redeploy any downstream application, service, or browser bundle that vendors an affected version, and audit transitive dependencies for pinned older releases. Where immediate upgrade is not possible, avoid processing Content Credentials manifests from untrusted sources and restrict outbound network access from the verification process so SSRF-triggered fetches cannot reach internal or cloud-metadata endpoints (egress allowlisting or blocking link-local/RFC1918 targets) - the trade-off is that legitimate remote-manifest resolution will break. For c2pa-web deployments, apply a strict Content-Security-Policy to blunt the script-injection step, accepting that CSP does not address the underlying SSRF.

More in C2Pa

View all
CVE-2026-48439 HIGH
7.5 Aug 11

Uncontrolled resource consumption in Adobe's CAI Content Credentials SDK enables remote unauthenticated attackers to exh

CVE-2026-48438 HIGH
7.5 Aug 11

Null pointer dereference in Adobe's Content Credentials SDKs (Rust SDK ≤c2pa-v0.90.5, JS SDK ≤@contentauth/c2pa-web@0.12

CVE-2026-48352 HIGH
7.5 Jul 14

Denial-of-service in Adobe's C2PA / Content Credentials SDKs allows a remote attacker to crash any application built on

CVE-2026-48351 HIGH
7.5 Jul 14

Denial-of-service in Adobe's Content Credentials (C2PA) SDK ecosystem lets a remote attacker crash any application that

CVE-2026-48295 HIGH
7.5 Jul 14

Credential disclosure in Adobe's CAI Content Credentials (C2PA) tooling - spanning the Rust SDK (c2pa ≤0.84.0), the JS S

CVE-2026-48287 HIGH
7.4 Jul 14

Arbitrary code execution in Adobe's Content Authenticity (CAI) Content Credentials tooling — the c2pa Rust SDK (≤0.84.0)

CVE-2026-48442 HIGH
7.1 Aug 11

Path traversal in Adobe's Content Credentials toolkit - spanning the c2patool CLI, the c2pa Rust SDK, and the @contentau

CVE-2026-48312 MEDIUM
6.8 Jul 14

Security feature bypass in Adobe's Content Credentials (C2PA) SDKs - the Rust SDK (≤0.84.0), JavaScript SDK (≤0.7.0), an

CVE-2026-48436 MEDIUM
6.5 Aug 11

Improper input validation across Adobe's Content Credentials JS SDK, Rust SDK, and command-line tool allows a remote una

CVE-2026-48445 MEDIUM
6.2 Aug 11

Integer overflow in Adobe's CAI Content Credentials SDK family (Rust, JavaScript, and CLI) allows a local attacker to cr

CVE-2026-48444 MEDIUM
6.2 Aug 11

Integer overflow in Adobe's Content Credentials ecosystem - spanning the Rust SDK (c2pa ≤ v0.90.5), JavaScript SDK (@con

CVE-2026-48443 MEDIUM
6.2 Aug 11

Uncontrolled resource consumption in Adobe's CAI Content Credentials ecosystem (c2patool CLI, Rust SDK, and JS SDK) allo

Share

CVE-2026-48290 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy