News: 1776081427

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Adobe finally patches PDF pest after months of abuse

(2026/04/13)


Adobe has released a fix for an Acrobat and Reader zero-day that [1]attackers had been exploiting for months .

The patch, [2]shipped on April 11 , addresses CVE-2026-34621, a critical vulnerability in Acrobat and Reader on Windows and macOS that can lead to arbitrary code execution. That's the polite way of saying a booby-trapped PDF could hand over the keys to the machine just by being opened.

In its advisory, Adobe says it is "aware of CVE-2026-34621 being exploited in the wild," which is doing a fair bit of reputational cleanup in a single sentence. Until now, there had been no public acknowledgment from the company that the bug even existed, let alone that attackers were actively using it.

[3]

The patch arrived a couple of days after external reporting put the campaign in the spotlight.

[4]

[5]

Malicious documents used heavily obfuscated JavaScript running through legitimate Acrobat APIs to gather system information from the host. Based on what it found, the malware could then decide whether to escalate, pulling down a second-stage payload capable of remote code execution or breaking out of Reader's sandbox.

[6]Months-old Adobe Reader zero-day uses PDFs to size up targets

[7]Anthropic: All your zero-days are belong to Mythos

[8]Attackers exploited this critical FortiClient EMS bug as a 0-day

[9]Unknown attackers exploit yet another critical SharePoint bug

Some targets were left with nothing more than a fingerprinting pass, while others were lined up for deeper compromise. That kind of triage suggests a campaign with specific interests rather than opportunistic spam, which lines up with the lures researchers observed. Some of the documents were written in Russian and referenced oil and gas sector themes, hinting at a more targeted victim pool without quite pointing a finger at who might be behind it.

According to researchers, evidence suggests the malicious activity stretches back to at least late 2025, giving attackers a comfortable runway of several months. During that time, the exploit blended into normal Reader behavior, sidestepping traditional defenses that are tuned to spot known signatures or obvious misbehavior.

The patch closes the hole, but it does not rewind the clock. Anyone who opened a malicious PDF during that window may already have been profiled or worse, depending on how interesting they looked to the attacker. Adobe has not said how many users might have been affected, how the flaw was discovered internally, or why acknowledgment lagged behind public reporting. The company still hasn't responded to The Register's questions.

[10]

Adobe may have closed the door, but not before plenty had already walked through it. ®

Get our [11]Tech Resources



[1] https://www.theregister.com/2026/04/09/monthsold_adobe_reader_zeroday_uses/

[2] https://helpx.adobe.com/security/products/acrobat/apsb26-43.html

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ad0TJZ51AeO1IngvtMaLLgAAABY&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ad0TJZ51AeO1IngvtMaLLgAAABY&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ad0TJZ51AeO1IngvtMaLLgAAABY&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://www.theregister.com/2026/04/09/monthsold_adobe_reader_zeroday_uses/

[7] https://www.theregister.com/2026/04/07/anthropic_all_your_zerodays_are_belong_to_us/

[8] https://www.theregister.com/2026/04/06/forticlient_ems_bug_exploited/

[9] https://www.theregister.com/2026/03/19/unknown_attackers_exploit_yet_another/

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ad0TJZ51AeO1IngvtMaLLgAAABY&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[11] https://whitepapers.theregister.com/



Paul Herber

Phew! Now we can all relax and go back to assuming that any random PDF we receive is safe and will not compromise any computer.

Forced Acrobat sucks

Anonymous Coward

Acrobat used to be essential. Now it's just a nuisance when business needs one of the enterprise features (and a web flow doesn't work for some reason).

Take document signing, for example. If you need it, you need it. If you're stuck, you're stuck.

We're still stuck because of partners.

Internally, we prefer signing with OpenPGP, which works on a hell of a lot more than PDF.

Can't wait for the day when Acrobat is completely gone. The world will be a lot better place when an "Acrobat document" or a "PDF document" is simply a document, and the things we need to do with documents are universal and cross platform.

Re: Forced Acrobat sucks

find users who cut cat tail

Adobe voluntarily removed its products from out OSes by discontinuing them in 2013. Occasionally, we need to deal with some of those features – either by taking a non-digital route or with the help of a colleague afflicted by a supported OS. Since it is just one of the hundreds of ways PDFs can be (and regularly are) broken, it is not a big deal.

Blackjack

Why are people still using PDF files?

Any given program, when running, is obsolete.