
Intune Proactive Remediation scripts to enforce patched Adobe Acrobat/Reader versions and disable JavaScript to mitigate CVE-2026-34621 exploitation.
This repository contains Microsoft Intune Proactive Remediation scripts to reduce exposure to Adobe Acrobat/Reader vulnerabilities by:
These controls can be used together:
Adobe released a security update for Acrobat and Reader addressing CVE‑2026‑34621, which Adobe confirmed is being exploited in the wild, and which can lead to arbitrary code execution. The fixed version for the Acrobat/Reader DC Continuous track is 26.001.21411. 1
In managed environments, having the latest installer available is not enough—devices may still run older builds. This repository helps ensure vulnerable versions are not left installed and enables an additional mitigation (disabling JavaScript) to reduce exposure immediately.
Detect-AdobeAcrobat.ps1Remediate-AdobeAcrobat.ps1DetectionJavaScript.ps1RemediateJavaScript.ps1Detect-AdobeAcrobat.ps1Purpose: Detect Adobe Acrobat installations below a defined minimum version.
Behavior:
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallHKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\UninstallDisplayName is like Adobe Acrobat*DisplayVersion against:
26.001.21411 (patched build for CVE‑2026‑34621) 1Exit codes:
0 = Compliant (not found OR version >= minimum)1 = Non-compliant (found with a lower version)Remediate-AdobeAcrobat.ps1Purpose: Remove Adobe Acrobat installations found on the device (Reader/Pro/Standard).
Behavior:
Adobe Acrobat* entries in both uninstall registry hivesUninstallString / QuietUninstallString regex (preferred)msiexec /x {GUID} /q /norestart3010 (reboot required) as successExit codes:
0 = Remediation completed successfully1 = Remediation completed with errorsNote: This remediation removes Acrobat. Make sure you also deploy the patched version (or preferred supported version) via your standard Intune application deployment process.
Disabling Acrobat/Reader JavaScript can reduce exposure to malicious PDF payloads that rely on JavaScript execution. This is meant as a rapid risk reduction measure while patching is being rolled out.
DetectionJavaScript.ps1Purpose: Verify that JavaScript is disabled for both Adobe Reader DC and Adobe Acrobat DC.
Registry keys checked:
HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\bDisableJavaScriptHKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown\bDisableJavaScriptExpected value:
bDisableJavaScript = 1Exit codes:
0 = Compliant (both keys exist and are set to 1)1 = Non-compliant (missing key and/or not set to 1)RemediateJavaScript.ps1Purpose: Enforce JavaScript disablement for both Reader and Acrobat DC by setting policy registry values.
Behavior:
bDisableJavaScript (DWORD) = 11 on any error; otherwise 0This approach gives immediate hardening while you ensure the patched version is deployed everywhere.
Some PDFs or enterprise workflows (forms, dynamic content, embedded scripts) can rely on JavaScript. Validate with key user groups before broad rollout.
If Acrobat was installed via non-MSI methods, GUID-based removal may fail and require a different uninstall strategy.
This project is licensed under the MIT License — feel free to use, modify and distribute.
Disclaimer
This repository contains generic, public best-practice scripts. It is not affiliated with any current or past employer or client. Created for educational and community purposes only.