
Key points
- Adobe Acrobat for Edge versions up to 154.0.4258.37 are affected by CVE-2026-75751.
- The vulnerability is rated 8.8 HIGH severity by the National Vulnerability Database.
- Exploitation requires user interaction to open a specifically crafted malicious document.
Adobe Acrobat for Edge contains a high-severity vulnerability that allows attackers to execute arbitrary code, according to the National Vulnerability Database. This flaw, tracked as CVE-2026-75751, affects software versions running up to 154.0.4258.37. Security teams should prioritize assessing their environments for these specific builds to determine exposure levels immediately.
The National Vulnerability Database rates the issue at 8.8, which falls within the high severity category. The underlying weakness is classified as CWE-787, an out-of-bounds write error. This type of memory corruption can lead to arbitrary code execution in the context of the current user. The potential impact is significant because it grants an attacker the same privileges as the user who opened the file.
Technical Context and Mechanics
The vulnerability is described as an out-of-bounds write issue. The National Vulnerability Database states that this flaw could result in arbitrary code execution in the context of the current user. The source material does not specify the exact component within the application where the write occurs. It only identifies the weakness type and the potential outcome of exploitation.
Who Is Affected
Organizations using Adobe Acrobat for Edge are exposed to this risk. Specifically, any deployment running version 154.0.4258.37 or any earlier release is vulnerable. The National Vulnerability Database explicitly lists these versions as affected. Teams must inventory their endpoints to identify which machines are running these specific builds. Users of newer versions are not mentioned as being impacted by this specific CVE.
Next steps
Administrators should verify the installed version of Acrobat for Edge across their infrastructure. Systems running version 154.0.4258.37 or earlier require immediate attention. Organizations should consult Adobe's security advisories for the latest status on remediation. If an update is available, it should be tested and deployed promptly. Until then, restricting the ability to open untrusted files may reduce risk.
Signals worth monitoring
Teams usually look for unexpected process spawning from the Acrobat executable. Check whether legitimate document viewing triggers unusual network connections to unknown external hosts. Look for attempts to write files to unexpected directories or modify system configurations. Monitor for high CPU usage during simple file operations. Containment typically involves isolating affected endpoints and blocking suspicious outbound traffic identified during initial triage.
What to do and how to stay safe: Adobe Acrobat
- Inventory all endpoints to identify installations of Adobe Acrobat for Edge version 154.0.4258.37 or earlier.
- Educate users to avoid opening PDF files from untrusted sources or unexpected email attachments.
- Monitor endpoint logs for anomalous behavior originating from the Acrobat process.
- Verify if the vendor has released a patched version and plan for deployment once confirmed.
Step-by-step guide: Emergency Patching Checklist for Critical System Fixes
General security guidance from the SecOps Monitor newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Which versions of Adobe Acrobat for Edge are vulnerable to CVE-2026-75751?
Versions up to and including 154.0.4258.37 are affected by this vulnerability, according to the NVD.
What is the severity rating of CVE-2026-75751?
The National Vulnerability Database rates the vulnerability as 8.8, which is considered high severity.
Does exploiting this vulnerability require user interaction?
Yes, exploitation requires a victim to open a malicious file, as stated in the NVD description.



