← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-8037 exploited? Yes: in CISA KEV since 7 Aug 2026

Gociux · Progress LoadMaster · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-8037, Progress LoadMaster Command Injection Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 7 Aug 2026, 64 days after it was published. It affects Progress LoadMaster. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 7 Aug 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity9.6CVSS 3.1 · critical
US federal due10 Aug 2026BOD 22-01 deadline

What it is

Progress LoadMaster contains a command injection vulnerability that allows an un-authenticated attacker to execute arbitrary commands on the LoadMaster appliance by exploiting unsanitized input in multiple command endpoints.

VendorProgress (9 exploited CVEs in KEV)
ProductLoadMaster
VulnerabilityProgress LoadMaster Command Injection Vulnerability
WeaknessCWE-77
Published4 Jun 2026
Added to KEV7 Aug 2026
Reported by (CNA)ProgressSoftware

What to do

  1. Check whether you run it. Look for LoadMaster in your asset inventory, including appliances and cloud images. Stack check lists every exploited Progress CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 4 Jun 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Progress.

References

Questions

Is CVE-2026-8037 being exploited?

Yes. CISA added CVE-2026-8037 to the Known Exploited Vulnerabilities catalog on 7 Aug 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-8037 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-8037?

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. Check Progress's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected LoadMaster and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2026 · Progress scorecard · act-now radar.

Running Progress in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →