JPCERT/CC Warns SiteGuard WAF Flaw CVE-2026-106931 Is Exploited

JPCERT/CC warns attackers are exploiting CVE-2026-106931, an OS command injection in SiteGuard Server Edition WAF that grants root or SYSTEM privileges.
Table of Contents
    Add a header to begin generating the table of contents

    Japan’s JPCERT/CC warned on October 14 that attackers are exploiting CVE-2026-106931, an operating system command injection flaw in SiteGuard Server Edition, a host-based web application firewall from EG Secure Solutions. The vendor has confirmed the exploitation but has not shared attack details.

    Command Injection in a Default-Enabled Statistics Feature

    The vulnerability sits in the product’s statistics feature, which is enabled by default. According to the JVN advisory, an attacker with low-level local access can run commands with root or SYSTEM privileges. The flaw has a CVSS 4.0 score of 8.5.

    The privilege jump is the central risk. A local account with limited rights, once it reaches the statistics feature, can take full control of the host running the firewall software. Because the feature is on by default, administrators who never changed the configuration are exposed without having enabled anything.

    What EG Secure Solutions Has and Has Not Said

    EG Secure Solutions confirms that exploitation is happening. It has not described who is behind the attacks, how many servers were affected, or what attackers did after gaining elevated privileges. Patches are available.

    A Two-Week Gap Between Customer Notice and Public Disclosure

    The vendor alerted customers with direct support contracts on September 29. Public disclosure followed on October 14, about two weeks later. In that interval, customers without direct support contracts had no formal notice, so some servers may have been compromised before most administrators knew the flaw existed.

    The sequence shows how a staged notification leaves a group of users uninformed while exploitation is already underway. The vendor has not said when it first saw attacks or whether the customer notice on September 29 was prompted by exploitation or by internal discovery.

    Save Diagnostics Before Patching

    The vendor tells administrators to save diagnostic information from the admin console before applying the update, because updating the software may erase traces of an attack. That instruction matters for any organization that needs to determine whether it was compromised before it patched. Once the update runs, the evidence that would show a prior intrusion may be gone.

    The guidance is unusual in that the standard remediation, patching, can itself destroy forensic artifacts. Administrators who patch without saving diagnostics risk concluding they were unaffected when they cannot actually tell.

    A Compromised WAF Host Puts the Protected Server at Risk

    SiteGuard Server Edition is a host-based web application firewall, meaning it runs on the same machine as the web server it protects. A compromise of the firewall host therefore puts the protected web server at risk as well, since the two share a system. An attacker who reaches root or SYSTEM privileges through the firewall component is positioned on the very machine the firewall was meant to defend.

    The Limits of a Local-Access Requirement

    The advisory describes the attacker as having low-level local access. That requirement narrows the pool of attackers compared with an unauthenticated network flaw, but it does not prevent exploitation in the real attacks JPCERT/CC and the vendor have confirmed. The sources do not say how the attackers obtained their initial local access, which leaves open whether they used stolen credentials, a separate vulnerability in the web application, or another route.

    An attacker who already controls a web application account on the server, for example, may meet the local-access condition. The vendor has not confirmed any such chain, and the sources do not describe one.

    What EG Secure Solutions Has Not Published About SiteGuard Attacks

    JPCERT/CC and EG Secure Solutions have published neither indicators of compromise nor a count of affected installations. The only concrete remediation guidance from the vendor is to save diagnostics, then patch. Until the vendor shares more detail about how the attacks work, administrators have to rely on the saved diagnostic data and their own logs to judge whether a host was exploited before the fix was applied.

    Related Posts