Arbitrary code execution in current-user context
Published Oct 13, 2026 · Updated Oct 13, 2026
Incorrect authorization in Adobe Experience Manager allows attackers to execute code in the current user's context without user interaction. The supplied record identifies no affected endpoint or incorrect authorization decision, and the inspected Adobe bulletins do not document this identifier's mechanism. Required privileges and request details remain unknown; the supplied record reports current-user code execution, not established host-wide control.
Summary
What happened
Incorrect authorization in Adobe Experience Manager allows attackers to execute code in the current user's context without user interaction. The supplied record identifies no affected endpoint or incorrect authorization decision, and the inspected Adobe bulletins do not document this identifier's mechanism. Required privileges and request details remain unknown; the supplied record reports current-user code execution, not established host-wide control.
The record
- CVE
- CVE-2026-75732
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- Adobe Inc.
- Product
- Adobe Experience Manager
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 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 <=6.5.25
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started