Skip to content

Security Reports disagree10 publishers 2 min read Published Updated

Chained PaperCut flaws let unauthenticated requests load attacker Java into the server process

Huntress has seen exploitation in two customer environments. One flaw hands over PaperCut's configuration without a login, the second turns that configuration into a class loader, so patching and config review are one job.

The Watch · Security desk

Send a correction

Illustration accompanying Chained PaperCut flaws let unauthenticated requests load attacker Java into the server process
Generated illustration

What happened

  • Huntress reports limited exploitation of PaperCut NG and MF in two customer environments, with attackers running Base64-encoded commands chained as "whoami & ver" to identify the account and operating system.
  • PaperCut has publicly disclosed two flaws behind the activity, CVE-2026-82078 rated CVSS 9.4 and CVE-2026-81578 rated CVSS 8.8, both affecting MF and NG.
  • watchTowr says attackers are chaining the two vulnerabilities together to bypass authentication and reach remote code execution on affected instances.
  • watchTowr also says it found multiple patch bypasses and one further authentication bypass, which it believes were likely addressed in the second emergency patch.
  • In an incident dated August 27, 2026, Huntress saw a different build of the Java payload that added tasklist to the command to capture running processes as well.

Why it matters

  • Who's exposed exposure watchTowr's Jake Knott frames the box as worth the chain twice over: an internet-facing pivot into the corporate network, and a document store if print retention is switched on, so the loss is network access and content together.
  • What it limits constraint Triage cannot lean on the application's own logs, since the payload removes them, which pushes verification onto host and network telemetry collected outside PaperCut.
  • Who has to decide decision Anyone who installed the first emergency fix has to decide again, because PaperCut's own second patch adds hardening beyond it, meaning "patched" now carries a date.
  • What it sets up precedent Two CVEs from one permission-check design, plus the bypasses watchTowr reported, set the expectation that further component and action pairs get tested the same way rather than that this class of bug is closed.

The authorization check reads the wrong object. A crafted request can name one page to be rendered in the response and a different page that owns the component or action actually executed, and PaperCut's permission test lands on the rendered page rather than on the code behind it [6]. That is the unauthenticated foothold.

CVE-2026-81578, scored 8.8, is that gap in the web management interface: unauthenticated remote requests reach administrative functions and trigger backend actions before access validation completes [3]. CVE-2026-82078, scored 9.4, sits in the database connection utilities, where the application instantiates driver classes from configurable driver names with no allowlist check [2]. Change the configuration without a login, then have the server load the class you named [16]. Huntress puts the end state as remote control over the trusted configuration and arbitrary Java code running inside the application's process [5]. The higher score is on the class loading; the half of the chain that deletes the login requirement is the 8.8 [15].

The payload Huntress recovered is a Java .class file, operating-system agnostic, running under Linux or Windows to fingerprint the machine and produce a directory listing, written to a file named Udydn.out under a /data/content/ path relative to the install directory [12]. It then deletes Udydn.out, the server's server.log, and /data/internal/derby.log [13].

PaperCut has not said what the malicious activity looked like [19], so the detection material in circulation is Huntress's artifact set plus whatever the server configuration itself shows. The database driver name is a stored, attacker-writable value, which makes reading that field, and the rest of the config, part of the same day's work as the patch [16]. Recommended containment: remove public exposure immediately, apply the patch, and restrict Application Server web access to trusted IP addresses or place it behind a VPN or another controlled administrative path [11].

What to watch

  • PaperCut publishing any detail on the intrusions it patched against; the only artifact set in public today came from Huntress.
  • Confirmation from watchTowr that its additional authentication bypass and the patch bypasses it found are actually closed by the second emergency patch.
  • Exploitation moving past the two environments Huntress named, or a working chain going public.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence85
Adoption70
Hype gap−10
Incentives40
Confidence78

Perspective Coverage

10 publishers
Builder
Builder 27%
Operator
Operator 60%
Investor
Investor 13%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Malicious actors are exploiting a newly patched security flaw in PaperCut NG and PaperCut MF to execute arbitrary code on susceptible instances.

    Reported Supported Source: thehackernews.comView cited source
  2. [2]

    CVE-2026-82078 (CVSS 9.4): an unsafe dynamic class loading vulnerability in the database connection utilities of PaperCut MF and NG; the application instantiates database driver classes based on configurable driver names without validating against an allowlist of approved drivers.

    Reported Supported Source: PaperCut advisory via thehackernews.comView cited source
  3. [3]

    CVE-2026-81578 (CVSS 8.8): an improper access control vulnerability in the web management interface of PaperCut MF and NG; under specific conditions, unauthenticated remote requests targeting administrative functions can trigger backend actions prior to the completion of access validation checks.

    Reported Supported Source: PaperCut advisory via thehackernews.comView cited source
  4. [4]

    PaperCut has publicly disclosed two flaws in NG and MF: CVE-2026-82078 and CVE-2026-81578.

    Reported SupportedView cited source
  5. [5]

    Huntress researchers John Hammond and Andrew Brandt said the vulnerability gives an unauthenticated attacker remote control over PaperCut's trusted configuration, which could be used to execute arbitrary Java code inside the application's process.

    Reported Supported Source: Huntress (John Hammond, Andrew Brandt)View cited source
  6. [6]

    Huntress: in unpatched PaperCut NG and MF, a crafted request can refer to one page that is rendered for the response and another page that owns the component or action being executed; PaperCut's authorization check could trust the rendered page and miss the permissions required by the component behind it, letting an unauthenticated request change the server configuration and reach sensitive endpoints that trigger unsafe actions and arbitrary code execution.

    Reported Supported Source: HuntressView cited source
  7. [7]

    PaperCut, an Australian company, released a second emergency patch that it said includes additional hardening beyond the original emergency patch.

    Reported SupportedView cited source
  8. [8]

    watchTowr said attackers are chaining together both vulnerabilities to bypass authentication and gain remote code execution on affected instances.

    Reported Supported Source: watchTowrView cited source
  9. [9]

    Huntress said it has observed limited exploitation in two customer environments, with attackers executing Base64-encoded commands on the targeted server, using a chained command "whoami & ver" to determine the user account and operating system.

    Reported Supported Source: HuntressView cited source
  10. [10]

    In an incident recorded on August 27, 2026, threat actors used a different version of the .class file running "whoami & ver & tasklist" to also capture the list of running processes.

    Reported Supported Source: HuntressView cited source
  11. [11]

    Organizations running PaperCut NG and MF are advised to remove public exposure immediately, apply the patch as soon as possible, and restrict PaperCut Application Server web access to trusted IP addresses or place it behind a VPN or another controlled administrative path.

    Reported SupportedView cited source
  12. [12]

    The attack deploys a Java .class file that is operating system agnostic and can run commands under Linux or Windows to fingerprint the machine and obtain a directory listing, writing the data to a file named "Udydn.out" in a "/data/content/" path relative to the program's installation directory.

    Reported Supported Source: HuntressView cited source
  13. [13]

    After collection, the .class file deletes "Udydn.out", the server's "server.log" file, and a "/data/internal/derby.log" file.

    Reported Supported Source: HuntressView cited source
  14. [14]

    Jake Knott, head of threat intelligence at watchTowr, said PaperCut is a prime target because it is both an internet-facing pivot into a corporate environment and a sensitive information treasure trove if printed documents can be stored and exfiltrated.

    Reported Supported Source: Jake Knott, watchTowrView cited source
  15. [15]

    The higher CVSS score in the pair, 9.4, is assigned to the class loading flaw, while the flaw that removes the authentication requirement is scored 8.8.

    Derived Supported
  16. [16]

    In the chain watchTowr describes, CVE-2026-81578 supplies the unauthenticated write to server configuration and CVE-2026-82078 converts a configuration value, the database driver name, into a class the server loads and runs.

    Derived Supported
  17. [17]

    Because the payload deletes the PaperCut server.log and derby.log files, absence of entries in those logs cannot be used to rule out compromise on an exposed instance.

    Derived Supported
  18. [18]

    watchTowr said it also discovered multiple patch bypasses and an additional authentication bypass vulnerability, all of which are likely to have been addressed as part of the second emergency patch.

    Reported Contested Source: watchTowrView cited source
  19. [19]

    PaperCut has yet to share details about the nature of the malicious activity weaponizing the flaws.

    Reported ContestedView cited source
  20. [20]

    Both disclosed flaws are exploitable expressions of one authorization design in which permission checks bind to the rendered page rather than the executed component, and watchTowr's discovery of further bypasses indicates other component and action pairs remain candidate paths.

    Derived Contested

Sources

10 independent publishers whose own reporting we read for this story.

  1. bleepingcomputer.com

    3 articles · August 30, 2026

    PaperCut warns of NG, MF flaw exploited in zero-day attacks
  2. blog.rapid7.com

    1 article · August 28, 2026

    PaperCut NG/MF Critical Zero-Day Exploited in the Wild
  3. helpnetsecurity.com

    2 articles · August 31, 2026

    Unknown PaperCut NG/MF vulnerability is under active attack
  4. huntress.com

    1 article · August 27, 2026

    PaperCut Zero-Day: Active Exploitation and Pre-Auth RCE
  5. scworld.com

    1 article · August 28, 2026

    PaperCut issues emergency patches for actively exploited critical vulnerability
  6. securityaffairs.com

    2 articles · August 30, 2026

    PaperCut Zero-Day Under Active Attack: Emergency Patch Released
  7. securityweek.com

    3 articles · August 31, 2026

    PaperCut Releases Emergency Patch for Exploited Zero-Day
  8. thecyberexpress.com

    1 article · August 31, 2026

    PaperCut Issues Second Emergency Patch as Researchers Break Fix for Exploited Zero-Days
  9. thehackernews.com

    4 articles · August 29, 2026

    PaperCut Zero-Day Exploited in Attacks, Affecting All NG and MF Versions
  10. therecord.media

    1 article · August 28, 2026

    PaperCut warns of hackers using printer management software flaw in attacks

Topics and entities