Daily Wire · Free EditionConfirmed Threats. Zero Noise.

The Exploit Bulletin

What Security Teams Must Act On Today

The Exploit Bulletin

Friday, August 28, 2026

3 items require action.

Remote Code ExecutioncriticalCVSS 9.4CVE-2026-82078CVE-2026-81578

Unsafe database driver class loading enables exploitation chain to code execution on PaperCut NG/MF servers (CVE-2026-82078)

PaperCut released an updated Emergency Patch (Release 2) on August 28 while confirming customer incidents from active exploitation, and internet-facing servers left unpatched and unrestricted remain open to compromise via a pre-auth exploitation chain.

PaperCut MF and NG instantiate database driver classes from configurable driver names without validating against an allowlist, letting an attacker who can manipulate configuration parameters execute arbitrary Java bytecode on the classpath as the PaperCut server process. Huntress reports the flaw is being chained (alongside CVE-2026-81578) into pre-authentication remote code execution against exposed servers.

Affected: PaperCut MF < 24.1.10, < 25.0.13, < 26.0.5; PaperCut NG < 24.1.10, < 25.0.13, < 26.0.5

How to Test

Check your Application Server version against the fixed releases (24.1.10 / 25.0.13 / 26.0.5) and determine whether its web interface is reachable from the public internet; PaperCut says to act now even if no suspicious activity has been observed, and to watch the bulletin for indicators of compromise as the investigation continues.

How to Patch

Upgrade to PaperCut MF/NG 24.1.10, 25.0.13, or 26.0.5, or apply the vendor's Emergency Patch Release 2 (recommended even if the original emergency patch was already applied), verifying installers against the published SHA256 checksums; immediately restrict the PaperCut server's web interfaces to trusted internal IP addresses using firewall rules or network access controls.

Remote Code ExecutioncriticalCVSS 9.3CVE-2026-74232

Factory C2 implant (yunmgrd) in Zbtlink and MoreQuick router firmware enables unauthenticated remote root (CVE-2026-74232)

VulnCheck added this to its known-exploited catalog on 2026-08-27 after sinkholing the implant's hardcoded C2 domain and watching live devices beacon in, meaning any team still running these routers has an unauthenticated root backdoor an attacker on the network path can hijack.

Multiple Zbtlink and MoreQuick router firmware images ship with a command-and-control implant, yunmgrd, that listens on an unauthenticated cleartext UDP channel tied to a hardcoded C2 domain. Anyone controlling that domain or the network path can run commands as root on the device; VulnCheck took over the domain and found live implants beaconing home.

Affected: Zbtlink L3_V2_8 firmware 3.0.0.4.528; Zbtlink WE826-T2 firmware 19.1101; Zbtlink ZBT-7628 firmware 1.0.0.2.007; Zbtlink ZBT-ZBT7621 firmware 1.0.0.3.001; MoreQuick MQAC-7620/MQAC-7620A/MQAP-7620/MQAP-7620A/MQAP-7628 firmware 1.0.0.2.000; AP522 firmware 1.0.0.2.014; AP7628 and HC5661A firmware 3.0.0.4.380; APG721B firmware 19.0809; HK300 firmware 1.0.0.2.032; MAP-N10 firmware 1.0.0.2.044

How to Test

Check whether your device model and firmware version match the affected list; inspect the device for a running yunmgrd process and monitor egress traffic for cleartext UDP beacons from the router to unknown external hosts, which indicates the implant is active.

How to Mitigate

No vendor fix is published. Block all outbound UDP from these routers to untrusted destinations at an upstream firewall, and plan to reflash with trusted third-party firmware or replace the device — the implant ships in the factory image, so a configuration change alone does not remove it.

Credential ExposurehighCVSS 8.9CVE-2025-69286

Personal API keys derivable from shared assistant links in RAGFlow (CVE-2025-69286)

Microsoft published a case study documenting RAGFlow compromise via its AI-infrastructure attack research, and any instance still exposing shared assistant or agent URLs on a pre-0.22.0 build is handing attackers the owner's API key.

RAGFlow before 0.22.0 generates personal API keys and assistant/agent share tokens with the same URLSafeTimedSerializer and predictable inputs, making the tokens mutually derivable. Anyone who obtains a shared assistant or agent URL can derive the owner's personal API key and gain full control of that account.

Affected: infiniflow RAGFlow < 0.22.0

How to Test

Confirm the running RAGFlow version is below 0.22.0, inventory any assistant/agent share URLs that have been distributed or exposed publicly, and review API access logs for API-key usage from unexpected sources.

How to Patch

Upgrade RAGFlow to version 0.22.0 or later, then rotate all personal API keys and invalidate previously issued assistant/agent share links, since keys derived from old share tokens remain valid until rotated.