Sensitive-memory disclosure via out-of-bounds file read
Published Jul 8, 2025 · Updated Jul 9, 2025
Out-of-bounds read in Adobe Substance 3D Viewer 0.22 and earlier allows attackers to disclose sensitive memory via a malicious file. Adobe identifies malicious-file processing as the trigger but has not disclosed the affected parser, file format, or code-level operation that reads past a buffer boundary. Exploitation requires a victim to open the file; the documented consequence is memory disclosure without data modification or service interruption.
Summary
What happened
Out-of-bounds read in Adobe Substance 3D Viewer 0.22 and earlier allows attackers to disclose sensitive memory via a malicious file. Adobe identifies malicious-file processing as the trigger but has not disclosed the affected parser, file format, or code-level operation that reads past a buffer boundary. Exploitation requires a victim to open the file; the documented consequence is memory disclosure without data modification or service interruption.
The record
- CVE
- CVE-2025-43584
- Published
- Jul 8, 2025
- Updated
- Jul 9, 2025
- Vendor
- Adobe
- Product
- Substance 3D Viewer
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 9, 2025Record 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.22
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.
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