Local application crash
Published May 12, 2026 · Updated May 12, 2026
Improper input validation in Adobe Content Credentials SDK 0.78.2 and 0.7.0 allows local users to crash applications via crafted data. Adobe identifies the affected component only at the SDK level and has not disclosed the specific parser, input field, or validation operation that mishandles the data. Exploitation requires local access but no privileges or user interaction, and the documented consequence is limited to terminating an application that processes the input.
Summary
What happened
Improper input validation in Adobe Content Credentials SDK 0.78.2 and 0.7.0 allows local users to crash applications via crafted data. Adobe identifies the affected component only at the SDK level and has not disclosed the specific parser, input field, or validation operation that mishandles the data. Exploitation requires local access but no privileges or user interaction, and the documented consequence is limited to terminating an application that processes the input.
The record
- CVE
- CVE-2026-34666
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Adobe
- Product
- Content Credentials SDK
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 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 <=0.7.0
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