Progress Kemp LoadMaster Flaw Hits CISA KEV After 792 R
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Friday added a critical-severity security flaw impacting Progress Kemp LoadMaster to its Known Exploited Vulnerabilities (KEV) catal
What Happened
CISA added the critical-severity vulnerability CVE-2026-8037 affecting Progress Kemp LoadMaster to its Known Exploited Vulnerabilities (KEV) catalog on Friday. The move follows reports of 792 exploit attempts against the flaw, signaling active and widespread targeting of the load balancer product.
Kemp LoadMaster is a widely deployed application delivery controller used for load balancing, SSL offloading, and traffic management in enterprise environments. Its position at the network edge means exploitation can have cascading effects on the applications it fronts.
Why It Matters
The inclusion in KEV is not procedural. Federal agencies are now under a binding operational directive to patch within a specified timeframe, but the KEV listing also serves as a de facto warning for private sector organizations.
Load balancers sit directly in the path of inbound traffic, often with elevated privileges and broad network access to backend systems. A successful exploit of CVE-2026-8037 can give an attacker an initial foothold that is difficult to detect because the appliance itself is rarely monitored with the same rigor as servers or endpoints.
The 792 exploit attempts number is significant. It indicates that the flaw was not merely present in a proof-of-concept. Attackers have operationalized the vulnerability at scale, and organizations running affected versions should assume they are targets.
Technical Details
The vulnerability is an unauthenticated remote code execution flaw. An attacker who can reach the Kemp LoadMaster management interface or the data plane can execute arbitrary commands without valid credentials. No user interaction or special privileges are required, which places it in the highest risk category for network-exposed appliances.
Affected versions are those running certain Kemp LoadMaster releases prior to the fixed builds. The advisory for CVE-2026-8037 includes the specific patch versions and a proof-of-concept exploit, which was published prior to the KEV listing. Organizations should cross-reference their deployed version against those patch levels immediately.
Indicators of compromise are not yet widely available, but administrators should review LoadMaster logs for unexpected administrative commands, new user accounts, or outbound connections from the appliance to unknown destinations.
Immediate Risk
The immediate risk is high. Given the 792 exploit attempts, the likelihood of active exploitation in a given environment is elevated. Any Kemp LoadMaster exposed to the internet or to untrusted networks should be considered at risk until patched.
Attackers who gain RCE on a load balancer can redirect traffic, intercept credentials, pivot to backend application servers, or deploy backdoors that persist through routine maintenance. The appliance is a trusted network component, so activity originating from it may escape typical security monitoring.
If your organization runs Kemp LoadMaster, verify the version immediately. If it falls within affected ranges, apply the vendor fix as an emergency change. If patching is not immediately possible, restrict access to the management interface and monitor the appliance for anomalous behavior.
Security Insight
The gap between a published vulnerability and its appearance in KEV is the period of greatest danger. The 792 exploit attempts likely occurred in a short window after the advisory was released, before CISA formalized the threat. This is a pattern we have seen with Fortinet and Citrix appliances: threat actors now automate exploitation of newly disclosed flaws within hours, not days.
The more important takeaway is strategic. Load balancers and other network-edge appliances are the new perimeter of compromise. They rarely receive the patching rigor applied to servers or endpoints, and they often run for years without version review. Organizations should inventory all network appliances with management interfaces, classify them by exposure, and establish a patch SLA of 72 hours for any flaw that hits KEV. Assume that anything with an IP address and a web login is a target, because the exploit attempts prove the attackers already have.
Further Reading
Never miss a security update
Get real-time security alerts delivered to your preferred platform.
Related News
A newly patched security flaw impacting on-premise versions of JetBrains TeamCity has come under active exploitation in the wild, according to the U.S. Cybersecurity and Infrastructure Security Agency
The U.S. Cybersecurity and Infrastructure Security Agency (CISA), on August 5, 2026, added three flaws to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation in t
N-able is warning customers that hackers are exploiting an authentication bypass vulnerability (CVE-2026-18577) affecting both hosted and on-premises N-central servers. [...]
Cisco is warning that a high-severity Secure Firewall Management Center (FMC) static credential vulnerability, tracked as CVE-2026-20316, was actively exploited in zero-day attacks to gain unauthorize