Code execution via undisclosed server-side request forgery
Published Jul 14, 2026 · Updated Jul 14, 2026
Server-side request forgery in Adobe Content Credentials SDK products allows local users to execute code through crafted web content. Adobe has not disclosed the vulnerable function, request-processing path, or how attacker-controlled input becomes a server-side request. Exploitation requires a victim to visit a maliciously crafted URL or compromised web page, and successful exploitation runs code in the current user's context.
Summary
What happened
Server-side request forgery in Adobe Content Credentials SDK products allows local users to execute code through crafted web content. Adobe has not disclosed the vulnerable function, request-processing path, or how attacker-controlled input becomes a server-side request. Exploitation requires a victim to visit a maliciously crafted URL or compromised web page, and successful exploitation runs code in the current user's context.
The record
- CVE
- CVE-2026-48290
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Adobe
- Product
- Content Credentials JS SDK
- Classifications
- CWE-918, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=@contentauth/[email protected]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo