Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

25 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-8037 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: UTA0533 (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalRemote Code Execpublic exploit

CVE-2026-8037

CVE-2026-8037 — OS Command Injection Remote Code Execution Vulnerability in Progress LoadMaster, ECS Connection Manager, Object Scale Connection Manager & MOVEit WAF

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-8037 in CISA KEV with required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

OS Command Injection Remote Code Execution Vulnerability in API in Progress ADC Products allows an un-authenticated attacker to execute arbitrary commands on the LoadMaster appliance by exploiting unsanitized input in multiple command endpoints

Published Jun 4, 2026Updated Aug 10, 2026Sources: NVD, Progress Software (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 7, 2026

EPSS

100%

top of FIRST's scoreset

Affects

Progress Software

5 products listed

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

PoC

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade LoadMaster to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Federal deadline Aug 10, 2026 — passed 32 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Progress Software	LoadMaster	V7.2.60.0	Vulnerable
Progress Software	LoadMaster	V7.2.45.12	Vulnerable
Progress Software	ECS Connections Manager	V7.2.60.0	Vulnerable
Progress Software	Object Scale Connection Manager	V7.2.60.0	Vulnerable
Progress Software	MOVEit WAF	V7.2.60.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.6	CVSS 3.1	critical	2.8	6	Progress Software (CNA)
9.8	CVSS 3.1	critical	3.9	5.9	NVD

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

Execute Unauthorized Code or Commands

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

CWE-77Command Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-248 · Command InjectionCAPEC-40 · Manipulating Writeable Terminal DevicesCAPEC-15 · Command DelimitersCAPEC-136 · LDAP InjectionCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-183 · IMAP/SMTP Command InjectionCAPEC-75 · Manipulating Writeable Configuration Files

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 7, 2026

Federal deadline

Aug 10, 2026

passed 32 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable LoadMaster, ECS Connections Manager, Object Scale Connection Manager, MOVEit WAF.
Monitor for scanner or exploit-pattern traffic after 25 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

UTA0533

ip192.42.116.10572
Tor Node List · Apr 1, 2026
ip192.42.116.5849
Tor Node List · Feb 24, 2026
ip146.70.139.15464
StopForumSpam-Firehol · Feb 1, 2024

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Aug 10, 2026 · NVD
Added to CISA KEV catalog
Aug 7, 2026 · CISA
Initial · CVE published
Jun 4, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

20×SVRS was changedJul 9, 2026 – Aug 29, 2026 · SOCRadar CTI
14×TweetsJul 14, 2026 – Aug 24, 2026 · SOCRadar CTI
3×ModifiedAug 7, 2026 – Aug 8, 2026 · SOCRadar CTI
1×2 times mentioned on 2 Telegram channelsAug 8, 2026 · SOCRadar CTI

References

7 on the record

community.progress.com/s/article/LoadMaster-Critical-Security-Bulletin-June-2026-CVE-2026-8037-CVE-2026-33691
Patch, Vendor Advisory, NIST
labs.watchtowr.com/enterprise-tech-in-shell-out-progress-kemp-loadmaster-uninitialized-heap-to-pre-auth-rce-cve-2026-8037/
Exploit, Patch, Third Party Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-8037
US Government Resource, NIST
www.esentire.com/security-advisories/progress-kemp-loadmaster-vulnerability-targeted-cve-2026-8037
Third Party Advisory, NIST, GITHUB
www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
US Government Resource
www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2026-8037
Vendor Advisory

Coverage

20 stories from the feeds we poll

15 more reports on this CVEShowing 5 of 20 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Progress Softwareevery CVE for this vendor
August 2026what else CISA listed
Remote Code Execsame class
CWE-77other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 3 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-8037 is OS Command Injection Remote Code Execution Vulnerability in Progress LoadMaster, ECS Connection Manager, Object Scale Connection Manager & MOVEit WAF, a critical vulnerability affecting LoadMaster, ECS Connections Manager, Object Scale Connection Manager, MOVEit WAF from Progress Software. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 25 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.