Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: public-exploit (5 articles)Clear

Critical FortiSIEM path traversal flaw gains public exploit enabling unauthenticated remote code execution

Fortinet patched CVE-2026-106173, a critical path traversal flaw rated 9.4 in FortiSIEM that lets an unauthenticated attacker execute commands through specially crafted packets, and researchers have now released a public proof of concept. The attacker connects to the gRPC service on TCP port 27918 and writes a file outside the intended directory, using a null byte in the query-id parameter to truncate the filename so the write lands on an existing path such as a Redis health-check script that cron runs every 60 seconds. FortiSIEM 7.5.0 is affected, 7.6 is not, and users should upgrade to 7.5.1 or above. Horizon3.ai published the research.

Check
Upgrade FortiSIEM 7.5.0 to 7.5.1 or above immediately, since a public proof of concept now exists, and restrict access to the gRPC service on port 27918.
Affected
FortiSIEM 7.5.0 lets an unauthenticated attacker write a file outside the intended directory through crafted packets to the gRPC service, achieving remote code execution via a cron-run script.
Fix
Apply the FortiSIEM 7.5.1 upgrade, restrict network access to the management and gRPC services, and review hosts for unexpected changes to cron-run scripts.

Public exploit gives pre-authentication root on AnyDesk for Linux through direct-connection heap overflow

Rick de Jager of the V12 security team disclosed a pre-authentication heap overflow in AnyDesk for Linux, and a working exploit called AnyPwn was published on GitHub on October 8. The flaw is in the session protocol's mode-5 stream packet handler, which adds a 16-byte header to the declared payload length using 32-bit arithmetic without an overflow check, so a crafted length wraps the allocation to a tiny buffer and a single byte overflows it. The exploit uses a ROP chain to run a command as root over direct TCP connections on port 7070. AnyDesk fixed it in Linux 8.0.3, released in June, and has not issued a formal advisory or CVE.

Check
Update AnyDesk for Linux to at least 8.0.3, ideally the latest 8.1.0, and until then block or restrict direct connections to TCP port 7070.
Affected
AnyDesk for Linux 8.0.2, and possibly 8.0.1, lets an unauthenticated attacker overflow a heap buffer over a direct connection and run code as root.
Fix
Upgrade AnyDesk Linux clients to 8.0.3 or later, restrict inbound access to port 7070 to trusted hosts, and prefer relay connections over direct ones.

Cisco warns of ClamAV flaws with public exploit code and no workaround

Cisco warned that public proof-of-concept code exists for two vulnerabilities in ClamAV, the widely used open-source antivirus engine, that a remote unauthenticated attacker can use to crash the scanning process and disrupt protection. Tracked as CVE-2026-20337 and CVE-2026-20338, the flaws are rated high severity on Windows because ClamAV runs there in a privileged security context, and medium on macOS and Linux where it runs with lower privileges. There are no workarounds, and Cisco is rolling out fixes in August across its Secure Endpoint Connector products, which embed ClamAV. Because ClamAV is bundled into many mail and file-scanning products, exposure extends well beyond Cisco.

Check
Update ClamAV and any products that embed it, including Cisco Secure Endpoint Connector, and prioritize Windows systems where the scanning process runs in a privileged context.
Affected
Systems running unpatched ClamAV or products that bundle it (CVE-2026-20337, CVE-2026-20338); a remote attacker can crash scanning to disable protection, with the highest risk on Windows and public exploit code available.
Fix
Apply the ClamAV updates as they ship, since there is no workaround, inventory the mail and file-scanning products that embed the engine, and monitor for scanning processes crashing unexpectedly.

Public exploit reaches PHP eval in vBulletin for unauthenticated code execution

Public exploit details released on July 27 show how an unauthenticated request can reach PHP's eval function inside vBulletin and run code on an unpatched forum server. The attack needs no account, administrative access, or interaction from another user, making any internet-facing vulnerable forum a direct target. SSD Secure Disclosure lists vBulletin 6.2.1 and earlier and 6.1.6 and earlier as affected, without giving a lower version boundary. Forum software is an attractive target because it is public by design, often runs with limited maintenance, and a single compromised server can host web shells, redirect visitors, or expose community member data. Administrators should confirm their version and patch level.

Check
Confirm the vBulletin version on any forum you run, apply the vendor's patches, and inspect the server for web shells and unexpected PHP files given that a public exploit exists.
Affected
Internet-facing vBulletin forums on 6.2.1 and earlier or 6.1.6 and earlier; an unauthenticated request reaches PHP eval for remote code execution, and working exploit details are now public.
Fix
Update vBulletin to a patched release, place a web application firewall in front of the forum, restrict server file writes, and monitor for unexpected processes spawned by the web server.

Public exploit runs commands as git on unpatched self-managed GitLab servers

A researcher at depthfirst published a working exploit on July 24 for a GitLab flaw patched on June 10, running commands as the git user on any self-managed 18.11.3 server that has not updated. Any authenticated user who can push to a project can trigger it: the attacker commits a crafted Jupyter notebook and opens its commit diff to leak a heap pointer, repeats until an automated probe locates libraries in memory, then fires the payload with two more notebooks. No administrator rights, runner access, or victim interaction are needed. The bug sits in the notebook renderer, which passes repository-controlled data to a parser inside a long-lived worker.

Check
Move self-managed GitLab to a supported release containing the June fix, and for Helm or Operator deployments verify the GitLab version inside the Webservice image rather than only the chart version.
Affected
Self-managed GitLab servers on 18.11.3 or other unpatched builds; any authenticated user able to push a project can run commands as the git service account, with public exploit code now available.
Fix
Upgrade to a fixed release, since no workaround is offered, and note GitLab did not classify the fix as a security issue, so track upstream library bumps rather than security advisories alone.