PaperCut AI Attack Hits 440 Orgs: What to Patch Now
An AI agent chained two PaperCut flaws to breach 440 print management systems across 48 countries, compromising 11 organizations in 26 seconds flat, and researchers say old fashioned defenses still stopped it cold.
A PaperCut AI attack campaign has compromised at least 440 instances of the popular print management software across 395 organizations in 48 countries, according to a technical disclosure from GreyNoise’s “Agents Gone Wild” report published September 9, 2026. The campaign chains two newly disclosed vulnerabilities, CVE-2026-81578 and CVE-2026-82078, and hands most of the exploitation work to an autonomous AI agent rather than a human operator sitting at a keyboard.
What makes this campaign different isn’t the bug class. Authentication bypasses and unsafe class loading are old problems. It’s the speed. GreyNoise documented one target going from an empty attack workspace to real world remote code execution in under four hours, with domain administrator access following roughly two hours after that. Once the campaign moved from testing to mass exploitation, 11 organizations were compromised in 26 seconds.
Nearly half of the confirmed victims, 204 of 440, sit in the education sector, a skew researchers attribute to PaperCut’s customer concentration in schools and universities rather than deliberate targeting. K-12 districts and major U.S. universities have already confirmed exploitation, per TheHackerNews’s coverage of the campaign, and CISA has given federal agencies until September 14, 2026 to remediate both flaws.
What Happened, in Order
The timeline reads fast even by 2026 standards. Huntress detected the first real world attack activity on August 26 and reproduced a full pre-auth remote code execution chain in its own lab within hours. PaperCut published its first emergency bulletin the next day, confirming active exploitation against customers.
The vendor’s first patch didn’t hold. Attackers found a bypass within days, forcing a second emergency release. By August 31, CISA had added both CVEs to its Known Exploited Vulnerabilities catalog with a September 14 remediation deadline for federal systems. GreyNoise says the AI orchestrated wave of attacks began that same day, from a single IP address it has since attributed to the campaign.
Federal deadline: CISA’s KEV listing sets September 14, 2026 as the hard remediation date for U.S. federal agencies running PaperCut NG or MF. Private-sector IT teams are treating it as the de facto industry deadline too.
PaperCut shipped a third emergency patch release on September 1 after researchers found additional attack paths in the second fix. Arctic Wolf confirmed active exploitation against education sector targets on September 5. GreyNoise’s full technical writeup landed September 9, and by September 10 and 11, BleepingComputer, TheHackerNews, and a wave of other outlets had made it the week’s dominant cybersecurity story.
The Two Flaws PaperCut Missed
Two separate bugs make the full attack chain possible. Neither is exotic on its own, but chained together they hand an unauthenticated attacker complete control of the server.
| Detail | CVE-2026-81578 | CVE-2026-82078 |
|---|---|---|
| Severity (CVSS v4.0) | 8.8 (High) | 9.4 (Critical) |
| Type | Authentication bypass | Unsafe dynamic class loading |
| Root cause | CWE-305 “Tapestry request confusion” in the Apache Tapestry framework PaperCut is built on | Database driver classes loaded by configurable name with no allowlist check |
| Effect | Unauthenticated requests can trigger admin functions | Attacker controlled config leads to arbitrary Java execution |
| Fixed in | 24.1.10, 25.0.13, 26.0.5 | 24.1.10, 25.0.13, 26.0.5 |
The Tapestry flaw validates the page a request renders rather than the underlying action it triggers, which lets an attacker slip an admin level command past the login wall entirely. Once inside, the second bug lets that attacker point PaperCut’s database connector at an arbitrary Java class, achieving code execution under the PaperCut server process’s own security context. No credentials required at any step.
Inside the AI Attacker’s Toolkit
GreyNoise’s telemetry, pulled from its Global Observation Grid sensor network, gives an unusually granular look at how the campaign was actually built. The attacker didn’t write custom exploit code by hand and didn’t rely on a single AI model to do everything.
- Orchestration: OpenAI’s Codex, used purely as agent scaffolding to sequence tasks, not to generate exploit code.
- Exploit writing: A DeepSeek model, which GreyNoise says the attacker chose specifically because it lacks the offensive security content restrictions U.S. frontier labs build into their models.
- Reconnaissance: The Netlas.io internet scanning API, used to build target lists from a compromised or self obtained API key.
- Post-exploitation: Publicly available tools, including Mimikatz, SharpHound, Certipy, BloodHound, Rubeus, Impacket, NetExec, and Ligolo-ng, pulled live from public GitHub repositories.
“Despite U.S.-based frontier model guardrails, adversaries are using a variety of large language models to conduct intrusions globally.” GreyNoise Research Team, Global Observation Grid, GreyNoise blogGreyNoise attributes the campaign to a likely Russian speaking actor, at medium confidence, based partly on a 28 country avoid list topped by Russia, China, Hong Kong, Thailand, and Iran, plus most CIS states. Notably, the agent’s own avoid list failed in several of those countries anyway, a detail GreyNoise flags as evidence that agentic operations can deviate from their intended parameters even when the operator tries to control them.The model choice question echoes a debate NeuralWired has tracked closely on the defender side too. OpenAI’s own first “Critical” rated model carries far tighter usage restrictions than the DeepSeek model chosen here, and reporting on gaps in frontier lab oversight shows why attackers keep finding a less restricted option to route around rather than trying to jailbreak a guarded one.Three Paths to Domain Admin
🔑Path A: Pass the HashLSASS memory and registry secrets harvested locally, then replayed against the domain controller.🧩Path B: noPacThe known CVE-2021-42278/CVE-2021-42287 chain, still effective against unpatched Active Directory environments.👑Path C: Direct CreationA new domain admin account created outright, when the compromised host was itself the domain controller.Every successful path ended the same way: a DCSync attack pulling a full NTDS.DIT credential dump for exfiltration, effectively handing the attacker every password hash in the domain at once.The Numbers Behind the Panic
Speed is the headline, but the funnel matters more than the fastest single case. Credential harvesting was observed at 280 of the 440 compromised instances. Operating system or domain secrets were pulled at 147. Full domain administrator access, the worst possible outcome, was reached at only 12 organizations.Defense still works: GreyNoise confirmed at least one target’s Cloudflare web application firewall fully defeated the AI driven attack chain before it could progress. Basic network hardening remains an effective control against agentic attackers, not an obsolete one.Context from outside the PaperCut campaign backs up the speed numbers rather than contradicting them. Anthropic’s own September 2026 threat intelligence report, published one day before GreyNoise’s writeup, disclosed banning 832 accounts for malicious cyber activity between March 2025 and March 2026, with 67.3% of those, 560 accounts, showing evidence of AI assisted attack preparation. Anthropic itself frames that figure as a self selected enforcement sample, not a population level measurement.CrowdStrike’s 2026 Global Threat Report puts a wider frame around the same trend, recording AI enabled adversary activity up 89% year over year, with 82% of detections involving no malware at all, just stolen credentials, and a fastest recorded breakout time of 27 seconds. Separately, the World Economic Forum’s Global Cybersecurity Outlook 2026 found 94% of surveyed cyber leaders already call AI the single biggest driver of change in their field.What Researchers Are Actually Saying
Not every voice in this story is willing to over-narrate what happened. Blackpoint Cyber, which independently confirmed parts of GreyNoise’s findings, is notably cautious about the attacker’s end goal.“At this time, we cannot confirm the exact end goal of this campaign.” The methodology “is consistent with initial access activity, but we do not yet have sufficient evidence to confirm whether they are operating as an initial access broker.” Nevan Beal, Principal MDR Analyst, Blackpoint Cyber, TheHackerNewsThe clearest pushback on the “AI changes everything” framing comes from Nathan House, founder and CEO of StationX, a cybersecurity training firm, and a working practitioner with three decades in the field.“When a number can’t survive a click to its origin, it’s marketing. The verified data shows AI rising in attacker tooling. The recycled data inflates that into a tidal wave. Both things are true at once, and only one belongs in your threat model.” Nathan House, Founder & CEO, StationX, StationXHouse points out that Anthropic’s own numbers actually show AI assisted phishing falling 8.6% over the same study period, even as AI use shifted deeper into post compromise account discovery, which rose 8.9%. That complicates any narrative that AI attacks are simply exploding across every category at once.Jacob Klein, Anthropic’s head of threat intelligence, offers a similar note of caution when describing how his own team evaluates misuse cases, in comments made about adjacent bioweapons related findings in the same report.“You are not seeing someone in a comic book kind of way say, ‘Hey, I want to build a biological weapon to kill everybody.’ It’s an incredibly nuanced situation.” Jacob Klein, Head of Threat Intelligence, Anthropic, La Voce di New YorkRead together, these voices point to a specific, narrower conclusion than the loudest headlines suggest. The GreyNoise report itself is primary source, IOC backed, and independently corroborated. But the leap from “the attacker picked an uncensored model” to “a coming safety shopping economy” is analyst interpretation layered on top of solid data, not a claim GreyNoise makes as a general trend. Overstating that leap risks pushing policy conversations toward restricting model access broadly, when the controls that actually worked here, CISA’s KEV listing driving urgency, a web application firewall, and basic credential rotation, had nothing to do with which language model the attacker used.It’s also worth remembering that this campaign didn’t start with AI. GreyNoise’s four hour and 26 second statistics describe the deployment phase. A skilled human operator still had to find and weaponize both CVEs before any agent was turned loose, work that closely echoes Anthropic’s earlier disclosure of a largely autonomous, state sponsored Claude Code campaign against roughly 30 organizations in November 2025. This is the clearest criminal, financially motivated follow-on to that pattern, and the largest one yet by victim count.What IT Teams Should Do Now
PaperCut has a history here. A 2023 exploitation chain, CVE-2023-27532, previously led to extortion campaigns, and defenders are watching this one for the same pattern. The response checklist is straightforward, even if the timeline to act on it is not.
- Confirm every PaperCut NG/MF instance is on Emergency Patch Release 3, versions 24.1.10, 25.0.13, or 26.0.5 or later.
- Remove PaperCut’s web management interface from direct internet exposure and put it behind a VPN or firewall allowlist.
- Rotate every credential on any PaperCut host that touched the internet between August 31 and September 9, since harvested credentials remain valid until manually changed.
- Treat any print or asset management server with SYSTEM level Windows privileges and Active Directory integration as a Tier 0 asset, regardless of its perceived business importance.
- If your PaperCut deployment is still on version 23 or earlier, isolate it now. Huntress data shows 47% of roughly 2,500 tracked installations remain on that unpatched branch, which has no fix available.
ShadowServer’s internet-wide scanning still counted more than 1,000 PaperCut NG/MF instances exposed directly to the internet as of early September, weeks into the patch cycle. That number, not the AI angle, is the more actionable warning for most security teams this week.Frequently Asked Questions
What is CVE-2026-81578?
CVE-2026-81578 is a high severity (CVSS 8.8) authentication bypass in PaperCut NG/MF’s web management interface, disclosed August 27, 2026. It lets unauthenticated attackers modify server configuration and, when chained with CVE-2026-82078, achieve full remote code execution. CISA added it to its KEV catalog August 31, 2026.How many organizations were affected by the PaperCut AI attack?
GreyNoise confirmed at least 440 compromised PaperCut instances across 395 identified organizations in 48 countries, with credential harvesting at 280 victims and full domain administrator access achieved at 12 organizations, as of its September 9, 2026 report.Why did the PaperCut attacker use DeepSeek instead of ChatGPT?
GreyNoise’s analysis states the attacker used a DeepSeek model specifically because it lacks the offensive security content restrictions imposed by U.S. frontier labs like OpenAI and Anthropic, while using OpenAI’s Codex only as an orchestration harness, not for exploit generation.Is PaperCut safe to use in 2026?
PaperCut NG/MF is safe if fully updated to Emergency Patch Release 3, versions 24.1.10 or higher, 25.0.13 or higher, or 26.0.5 or higher, and not exposed directly to the internet. Roughly 47% of tracked installations still run version 23 or earlier, which has no available patch and should be isolated immediately.How fast can AI agents hack a company?
In the PaperCut campaign, GreyNoise documented AI agents achieving remote code execution against a real victim in under four hours from a standing start, domain administrator access as fast as five minutes after initial access, and 11 separate organizations compromised within 26 seconds once the full campaign launched.Did traditional security tools stop the AI-driven attack?
Yes, in at least one confirmed case. GreyNoise reported that a target’s Cloudflare web application firewall fully blocked the AI orchestrated attack chain, showing that conventional hardening, network segmentation, and credential hygiene still function against agentic AI attackers.What is the CISA KEV deadline for PaperCut?
CISA added CVE-2026-81578 and CVE-2026-82078 to its Known Exploited Vulnerabilities catalog on August 31, 2026, setting September 14, 2026 as the remediation deadline for U.S. federal agencies. Most private-sector security teams are treating it as the practical industry deadline as well.Conclusion: A Faster Clock, Not a New Rulebook
The PaperCut campaign is genuinely new in one respect: it’s among the first disclosures to put a stopwatch on an AI driven intrusion, from empty workspace to domain admin, with minute-by-minute telemetry instead of a summary statistic. That level of detail is exactly why this story is outperforming last year’s AI hacking headlines in pickup and search interest.But the underlying lesson is closer to an update than a rewrite. The bugs are conventional. The privilege escalation paths, pass the hash, noPac, direct account creation, are all years old. What changed is how little time defenders now have between disclosure and exploitation at scale. Patch cadences built around weeks no longer match a threat model built around hours.Watch For01 Whether the September 14, 2026 CISA KEV deadline actually drives federal remediation, or whether a meaningful share of the roughly 1,000 exposed instances ShadowServer found are still online after the date passes.02 The durable, unpatchable population running PaperCut version 23 or earlier, currently 47% of Huntress’s tracked base, which has no fix path and will remain a target indefinitely.03 Whether the “model shopping” narrative around DeepSeek hardens into export control or procurement policy debates that target model access broadly, rather than the patch management fundamentals that actually stopped this campaign in at least one confirmed case.Stay ahead of the curve. More on AI security and threat intelligence at NeuralWired.Explore Cybersecurity1 thought on “PaperCut AI Attack 2026: 440 Orgs Hacked, Patch Now”
Leave a Comment
Pingback: Berlin Ransomware Attack 2026: 1.4M Files Leaked Online - NeuralWired