Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Use‑After‑Free RCE in Adobe Acrobat Reader DC (CVE‑2026‑81975) Threatens Endpoints

Adobe disclosed a use‑after‑free remote code execution flaw (CVE‑2026‑81975) in Acrobat Reader DC that can be triggered when a user opens a malicious PDF or visits a crafted page. The vulnerability highlights the importance of rapid patching and evidence‑based vulnerability management for audit readiness.

Verisq™ Intelligence · 📅 September 10, 2026 · 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
zerodayinitiative.com

Use‑After‑Free RCE in Adobe Acrobat Reader DC (CVE‑2026‑81975) Threatens Endpoints

What It Is — A use‑after‑free flaw in the handling of Annotation objects allows a remote attacker to execute arbitrary code on Adobe Acrobat Reader DC when a user opens a malicious file or visits a crafted web page.

Exploitability — Requires user interaction; CVSS 7.8 (High) with network‑local vector, low complexity, and high confidentiality, integrity, and availability impact. No public exploit is known, but a proof‑of‑concept has been demonstrated.

Affected Products — Adobe Acrobat Reader DC (all supported versions prior to the September 2026 security update).

Why It Matters for Trust & Control Assurance

  • Underscores the need for continuous vulnerability‑management and rapid patching as a core control objective across frameworks.
  • Timely deployment of Adobe’s update provides concrete, auditable evidence that an organization is meeting its “Patch Management” and “Secure Configuration” controls.
  • Documented remediation timelines strengthen the audit trail and demonstrate due‑diligence to regulators and enterprise customers.

Recommended Actions

  1. Apply Adobe’s September 2026 security update to every Acrobat Reader DC installation without delay.
  2. Use automated asset‑inventory and endpoint‑scanning tools to verify that the patch is installed across the environment.
  3. Record remediation dates and supporting logs in your control repository to evidence compliance.
  4. Enhance your vulnerability‑scanning rules to specifically test for PDF annotation handling issues.

Source: Zero Day Initiative Advisory – ZDI‑26‑667

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-667/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →