SecurityAffairs and Cyber Kendra reported the same claimed capability and that no vendor fix and no CVE were public at the time they checked. Exploitation requires SMTP reachability to a Zimbra server that has the optional zimbra-snmp package installed, snmp_notify enabled, and swatchdog running.
Public code, claimed to work against fully patched Avast on patched Windows 11 25H2.
GenDigital Avast Antivirus, endpoint antivirus software on Windows desktops.
Local SYSTEM command execution from a standard Windows account
An ordinary local privilege escalation lands with a fix attached. This one has the code in public and nothing to install: the vendor had shipped no fix and there was no CVE when the outlets that covered it checked. The component doing the escalating is the security product itself, which is on the endpoint precisely because someone decided a standard user should not be able to do this.
The proof of concept abuses the Avast Sandbox to read the Windows SAM database and start a SYSTEM shell. The entry requirement is code execution as a standard local user on a machine with Avast installed — no administrator, no second bug, no user prompt in the middle.
The repository claims the exploit works against fully patched Avast on patched Windows 11 25H2, and two outlets reported the same claimed capability along with the absence of a vendor fix or CVE at the time they looked.
We are carrying this as provisional and want to be exact about why: nobody here ran it. The capability rests on the repository's own description plus secondhand reporting. What would settle it is a reproduction on a current Avast build showing the sandbox path still reachable from an unprivileged token.
One gap worth stating rather than writing around: our privilege surface could not reach CISA KEV or several other sources this run, so we cannot tell you whether anyone is tracking this as exploited in the wild. Absence of that line here is a blocked fetch, not a negative result.
Only with the optional zimbra-snmp package installed, snmp_notify enabled, and swatchdog running — which is the first thing to check, in both directions.
Zimbra Collaboration Suite, a self-hosted enterprise email and collaboration server.
Unauthenticated operating-system command execution as the zimbra service user
CERT Polska confirms active exploitation, unauthenticated shell execution as zimbra, the required configuration, and forensic artifacts for detection.
CERT Polska confirms active exploitation: attacker-controlled service-status text arriving over SMTP is processed by the enabled SNMP notification path, a command is injected, and it runs as the zimbra service account. Their write-up includes forensic artifacts, which is what to use if the preconditions match your install.
The preconditions are genuinely narrow — the optional zimbra-snmp package, snmp_notify turned on, swatchdog running — and that is why the reach here is niche rather than broad. It is also not a configuration most administrators can recall from memory, and recent reporting counts compromised internet-facing instances in the hundreds.
Scope: this answers for the patched 10.1.20 SNMP notification path I could read; rollback enforcement and alternate-interface completeness were not established.
sudo, the command-delegation and privilege-control utility used on Unix and Linux systems.
sudo's ptrace-based interceptor checked the execve family but not execveat, so a denied executable invoked through execveat — or through fexecve, which is implemented on top of it — runs without a policy check and without the subcommand logging that would have recorded it. It runs with the authorized command's runas identity, which in most real sudoers rules is root.
The upstream commit is explicit that sudo had deliberately allowed execveat through, and adds path resolution and intercept handling for it. The affected enforcement modes, intercept and log_subcmds, are optional — this only bites where someone chose them, which is to say where someone was specifically trying to contain a command they had to allow.
sudo-rs, the Rust sudo and su implementation shipped by Ubuntu 26.04 LTS.
Ubuntu describes a time-of-check/time-of-use race in sudo-rs sudoedit path handling: a local user granted the right to edit specific named files can win the race and have files placed in directories of their choosing instead. The point of a fine-grained sudoedit rule is that the list of files is the boundary, and this removes the boundary while leaving the rule looking intact.
Ubuntu says the issue only affects systems configured with fine-grained sudoedit file editing permissions, which is not the default configuration.
The step nobody has written down is which target turns arbitrary privileged placement into reliable root execution on a stock 26.04 host — the notice does not say, and until someone does, this is a boundary failure rather than a demonstrated escalation.
Pollen Robotics Reachy Mini, a small robot whose daemon exposes Bluetooth setup and command services on the robot host.
The CMD_ handler in the robot's Bluetooth command service joins attacker-controlled input into a script path and calls sudo on the result. Absolute paths and ../ traversal both escape the commands/ directory the design assumed, so anything already on the filesystem ending in .sh can be selected. Reaching it takes Bluetooth range and an authenticated command session.
The reason to watch this rather than file it is composition. JFrog names a separate media-sounds upload flaw as one way to get a .sh file onto the device, and describes a Bluetooth authentication bypass as the remaining step toward compromise with no credentials at all. Each piece is documented; the assembled version is what would matter.
The vendor advisory carries failing regression tests for both relative and absolute traversal payloads, and the public fix commit strips slashes and constrains command names to a basename character set before joining them under commands/.
A specialized robot is a small population, and that is the honest reason this sits here rather than higher.
No additional findings today.
Returned a preamble and no conclusion. No signed-component revocations or bootloader changes were reported to us, but nobody finished looking.
No new capability-changing frame found; the accessible upstream material was maintenance and robustness work or non-radio router management. Two hostap commits — PMKSA entry removal and Extended RSN Capabilities parsing — could not be retrieved, so this is not a fully quiet claim either.
Nothing new. The closest items were routine Chrome and Mozilla advisories with bug details still restricted. The August Android vulnerability table again failed to render in both the English and Chinese pages, which is the one thing that would have made this a clean quiet claim.
Returned a preamble and no conclusion. Unchecked, not quiet — and the open question about the remaining Fireware 2026.2.2 CVEs stays open, since the WatchGuard item this week's JPCERT report carries is a different advisory.
Returned a preamble and no conclusion. Treat as unchecked.
No new unauthenticated-to-execution primitive on an internet-facing appliance. The Bishop Fox NetScaler follow-up confirms the CVE-2026-8452 patch is comprehensive and contributes only a 512/513-byte patch-state oracle for target selection; the exploited Cisco ASA/FTD SSL VPN bug has not been re-rated. CISA returned 403 for every ICS advisory fetch, so Hitachi Energy APM Edge and Johnson Controls Metasys went unread rather than closed.
There is no September Android bulletin yet — the 2026-09-01 URL 404s and August (published 2026-08-03) is still the index's latest. Samsung remains on SMR-AUG-2026 with nothing remote beyond a user-interaction Dialer issue, and no September Qualcomm bulletin exists. New adbd proof-of-concept code for CVE-2026-0073 adds mDNS port discovery and PTY shells but keeps the same LAN-peer, wireless-debugging-enabled, previously-paired preconditions.
Returned a preamble and no conclusion. Original-research coverage for the day is unverified.
fullchain.sh follows the day’s disclosures from bug to shell — what each one enables, what it links to, and where the fix left the primitive in place. A CVE is an input, not an event. When nothing qualifies, the brief says so. Every morning.