C2paApplication · Adobe
CVE-2026-48290
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCAI 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCAI Content Credentials contains a Server-Side Request Forgery (SSRF) vulnerability that allows attackers to make the server perform arbitrary requests to internal or external resources. The scope is changed, meaning the vulnerability impacts components beyond the original service. Combined with the arbitrary code execution mention and CVSS 8.2, this suggests the SSRF may enable chaining to internal services or deserialization endpoints to achieve code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
C2paApplication
<= 0.84.0<= 0.7.0<= 0.17.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed C2pa productsRun commands to detect installed packages: for Adobe C2pa check node_modules/c2pa or pip list/cargo list depending on implementation; for Adobe C2pa Web check package.json or npm list; for C2patool run 'c2patool --version' or check installed binariesAffected if Any of the three products (Adobe C2pa, Adobe C2pa Web, or C2patool) are found installed on the system
-
Check product version against affected rangesCompare installed version to affected ranges: Adobe C2pa version <= 0.84.0, Adobe C2pa Web version <= 0.7.0, or C2patool version <= 0.17.0 indicates the vulnerable version is installedAffected if Installed version is at or below 0.84.0 for C2pa, 0.7.0 for C2pa Web, or 0.17.0 for C2patool
-
Verify URL/content fetching functionality is usedInspect application configuration or code that uses the C2pa library to determine if it processes external URLs for content credentials, manifests, or remote assets - look for C2pa.create() or similar API calls that accept remote URLsAffected if The application uses C2pa APIs to fetch or validate content from user-controlled or external URLs, enabling the SSRF attack surface
-
Check for network-accessible C2pa service endpointsReview web server or API configuration to identify if C2pa Web component exposes endpoints that accept URLs as input, or if C2patool is run as a network serviceAffected if C2pa Web or C2patool is configured as a network-accessible service that processes URLs from request parameters or API calls
You are affected if any Adobe C2pa, Adobe C2pa Web, or C2patool version at or below the affected thresholds is installed AND the product processes external URLs through its content credentials functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based URL validation for all user-controlled URLs, restrict server-side request capabilities to necessary domains only, and apply network segmentation to limit SSRF impact on internal infrastructure.
Fix this in C2pa
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data