Security-feature bypass via undisclosed design flaw
Published Sep 9, 2025 · Updated Sep 9, 2025
Secure-design failure in Adobe Acrobat Reader 25.001.20672 and earlier allows local users to bypass a security feature. Adobe has not disclosed the affected component or the design operation that mishandles input, so the bypass mechanism is not public. Local access is required, but neither authentication nor user interaction is required; exploitation can make an integrity-affecting change without crossing a security boundary.
Summary
What happened
Secure-design failure in Adobe Acrobat Reader 25.001.20672 and earlier allows local users to bypass a security feature. Adobe has not disclosed the affected component or the design operation that mishandles input, so the bypass mechanism is not public. Local access is required, but neither authentication nor user interaction is required; exploitation can make an integrity-affecting change without crossing a security boundary.
The record
- CVE
- CVE-2025-54255
- Published
- Sep 9, 2025
- Updated
- Sep 9, 2025
- Vendor
- Adobe
- Product
- Adobe Acrobat Reader
- Classifications
- CWE-657
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2025CVE publishedPublication date reported by the CVE source.
- Sep 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 <=25.001.20672
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