Memory disclosure via heap buffer overflow
Published Oct 15, 2025 · Updated Oct 15, 2025
Heap-based buffer overflow in Adobe Bridge 14.1.8, 15.1.1 and earlier allows attackers to disclose memory via a malicious file. Adobe identifies the flaw as occurring when Bridge opens a crafted file but does not disclose the affected parser, file format, or precise out-of-bounds operation. Exploitation requires a victim to open the file, and the reported consequence is sensitive-memory disclosure without integrity or availability impact.
Summary
What happened
Heap-based buffer overflow in Adobe Bridge 14.1.8, 15.1.1 and earlier allows attackers to disclose memory via a malicious file. Adobe identifies the flaw as occurring when Bridge opens a crafted file but does not disclose the affected parser, file format, or precise out-of-bounds operation. Exploitation requires a victim to open the file, and the reported consequence is sensitive-memory disclosure without integrity or availability impact.
The record
- CVE
- CVE-2025-54278
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- Adobe
- Product
- Adobe Bridge
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 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 <=14.1.8, 15.1.1
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