CT
CyberTimes
← Back to Threat Watch
adobe readerzero daypdf exploitApril 9, 2026 · CyberTimes Security Team

Adobe Reader Zero-Day Actively Exploited via Fake Invoice PDFs — No Patch Available Yet

A sophisticated zero-day vulnerability in Adobe Reader is being weaponized in the wild, and the most alarming part is that there is no patch yet. Security researchers at EXPMON confirmed the exploit w

TL;DR — 15 Second Read

  • A previously unknown zero-day vulnerability in Adobe Reader has been actively exploited since at least December 2025 through maliciously crafted PDF files, with no patch currently available.
  • The exploit is delivered via fake invoice PDFs that auto-trigger obfuscated JavaScript to harvest sensitive information and pull additional payloads from an attacker-controlled server.
  • The vulnerability abuses privileged Acrobat APIs and is confirmed to work on the latest fully updated version of Adobe Reader, making all current users potentially at risk.
  • The attack chain is designed to escalate toward remote code execution (RCE) and sandbox escape (SBX), with Russian-language lures targeting the oil and gas sector observed in the wild.
Severity🔴 CRITICAL
CVSS Score9.1/10
ExploitedYes — active
Fix StatusNo patch yet
If you use any version of Adobe Reader, including the latest release as of April 2026

A sophisticated zero-day vulnerability in Adobe Reader is being weaponized in the wild, and the most alarming part is that there is no patch yet. Security researchers at EXPMON confirmed the exploit works against the latest fully updated version of Adobe Reader, meaning millions of users across the globe are currently exposed with no vendor fix to fall back on.

The attack was first detected when a malicious PDF file named "Invoice540.pdf" surfaced on VirusTotal in late November 2025. A second sample appeared in March 2026, confirming an ongoing and active campaign. Cybersecurity, information security, and digital security communities are now on high alert as this unpatched flaw continues to be exploited in the wild.


Affected products

  • ·Adobe Reader (all versions including latest as of April 9, 2026)

How to Fix

Step-by-step remediation

Since no official patch is available, the most effective defense right now is disabling Adobe Reader's JavaScript engine entirely. To do this, open Adobe Reader and navigate to Edit → Preferences → JavaScript, then uncheck the box labeled "Enable Acrobat JavaScript". This directly cuts off the exploit's execution path.

Next, harden the application's sandbox settings. Go to Edit → Preferences → Security (Enhanced) and verify that both "Enable Protected Mode at startup" and "Enable Enhanced Security" are active. These settings restrict what processes Adobe Reader can spawn and which network connections it can initiate.

For enterprise environments, IT administrators should push a Group Policy or configuration management update to enforce these settings across all endpoints, and block outbound traffic to the known C2 IP 169.40.2[.]68 at the firewall level.

As a broader interim measure, consider routing all PDF opening through browser-based viewers or sandboxed environments. Tools like Windows Sandbox, any.run, or corporate DLP solutions that can inspect PDF content before delivery offer an additional layer of internet security protection while the vendor response is pending.


What happened

The zero-day targets a flaw in Adobe Reader that allows attackers to execute privileged Acrobat APIs without authorization — functionality that should be restricted to trusted, signed processes. By embedding obfuscated JavaScript inside a carefully crafted PDF, threat actors bypass Adobe's internal security controls entirely.

Once a victim opens the malicious file, the JavaScript executes automatically and silently. It begins harvesting local system data and sensitive information, then reaches out to a remote command-and-control server at IP 169.40.2[.]68:45191 to receive additional JavaScript payloads. Researchers believe these secondary payloads are designed to trigger remote code execution (RCE) and sandbox escape (SBX) exploits, though the exact next-stage payload was not recovered due to environment fingerprinting by the attacker's server.

The malware operators appear to be conducting targeted campaigns as well. Security researcher Gi7w0rm noted that observed PDF samples contained Russian-language lures referencing geopolitical events in Russia's oil and gas sector — a hallmark of nation-state-adjacent threat actors engaging in targeted intelligence collection.

Real-World Impact

This vulnerability represents one of the most serious document-based threats seen in recent years. Adobe Reader is installed on hundreds of millions of devices worldwide — in corporate environments, government agencies, hospitals, and individual systems — making the attack surface enormous. Because the exploit works on the latest patched version, standard update hygiene provides no protection at all.

The social engineering element compounds the risk significantly. Disguising the payload as an invoice PDF is a well-established and highly effective lure — it targets a document type that employees open daily without suspicion, particularly in finance, procurement, and operations teams. Organizations in the energy sector, given the Russia oil and gas targeting context, face especially elevated risk at this time.

The potential for the attacker to pivot from data harvesting to full remote code execution means that a single employee opening one PDF could result in complete network compromise, credential theft, ransomware deployment, or long-term espionage access. In terms of computer security and network security risk, this is a critical-severity event.

Technical Details

The exploit abuses an unpatched flaw in Adobe Reader's JavaScript engine that allows execution of privileged Acrobat APIs — internal functions that should only be accessible to trusted, signed Adobe processes. The attack uses a multi-stage architecture: Stage 1 is the initial exploit PDF, which uses heavily obfuscated JavaScript to bypass detection, fingerprint the local environment, and exfiltrate system information. Stage 2 involves receiving additional JavaScript code from the C2 server at 169.40.2[.]68:45191, which researchers believe facilitates RCE and SBX. The first malicious sample (Invoice540.pdf, SHA256: 54077a5b15638e354fa02318623775b7a1cc0e8c21e59bcbab333035369e377f) appeared on VirusTotal on November 28, 2025. A second sample (SHA256: 65dca34b04416f9a113f09718cbe51e11fd58e7287b7863e37f393ed4d25dde7) was submitted March 23, 2026. The gap between samples suggests an evolving campaign rather than a one-off incident. The server did not respond with a payload during sandbox analysis, indicating the operators filter requests based on system fingerprinting criteria — a technique used to avoid detection in controlled analysis environments.

🛡️ Prevention Tips

Never open PDF attachments from unknown or unexpected senders, even if the file name appears routine like an invoice or receipt. Attackers deliberately choose generic, trusted-looking file names to lower a victim's guard.

Disable JavaScript in Adobe Reader immediately using the steps outlined above — this is the single most impactful mitigation available right now given the nature of this zero-day.

Enable email security gateway filtering that strips or sandboxes PDF attachments before they reach end users, particularly for finance and operations teams who regularly handle invoice documents.

Keep threat intelligence feeds active and subscribe to Adobe's security notification service so your team is alerted the moment an emergency patch drops. In high-risk sectors, consider issuing an internal advisory to all staff warning them about suspicious PDF files until the vulnerability is resolved.

Implement application whitelisting or behavior-based EDR solutions that can detect and block unauthorized JavaScript execution launched from within document viewer processes — a pattern that deviates from normal data security baselines.


FAQs

Is there a patch available for this Adobe Reader zero-day?

No. As of April 9, 2026, Adobe has not released a patch for this vulnerability. The exploit is confirmed to work on the latest fully updated version of Adobe Reader. Users should apply the interim mitigations listed above and monitor Adobe's security bulletins for an emergency update.


How does the attack start — do I have to do anything to trigger it?

Yes, you need to open the malicious PDF in Adobe Reader for the exploit to trigger. The attack relies on social engineering — typically a fake invoice PDF sent via email — to trick users into opening the file. Once opened, the embedded JavaScript executes automatically without any further user interaction.


Will disabling JavaScript in Adobe Reader protect me completely?

Disabling JavaScript significantly reduces your risk since this specific exploit relies on executing JavaScript within the PDF. However, no mitigation is 100% foolproof. Combining JavaScript disabling with Protected Mode, Enhanced Security settings, and general caution with PDF files provides the strongest available defense right now.


Read Next