Exploited CVEs / Progress / CVE-2026-8037

CVE-2026-8037

Progress LoadMaster Command Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-08-10 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Progress Security Advisories, linked below.

Risk summary

In the top 10 of the Senserva CVE Ranking (as of 2026-08-13)
CriticalCISA KEV
9.8
CVSS base
99%
EPSS exploit probability
Critical
Severity
2026-08-07
Added to KEV
2026-08-10 (past due)
CISA due date

Actively exploited Progress LoadMaster vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-08-07.

CISA required actionOfficial fix for CVE-2026-8037Admin questions#1 hottest CVE right now
Senserva AI Opinion and rich prompt for CVE-2026-8037

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
The fix ships from the vendor: Progress Security Advisories.
Do this now: Federal remediation deadline 2026-08-10; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-8037

Published
2026-08-07
Last revised
2026-08-07
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is CISA adding CVE-2026-8037 to the KEV catalog on 2026-08-07, meaning active exploitation is confirmed. That same day Severity jumped from 0.0 to 9.8 and EPSS scored at 84.8%, then climbed to 99.3% on 2026-08-08. The direction is sharply upward, so prioritize patching today.

0%25%50%75%100%CISA KEVCISA KEV on 2026-08-072026-08-07: EPSS 85%2026-08-07: EPSS 85%2026-08-08: EPSS 99%2026-08-08: EPSS 99%EPSS 99%2026-08-072026-08-08

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-08-07 CVSS 0.0 to 9.8; EPSS first scored at 84.8%; added to the CISA KEV catalog by CISA
  • 2026-08-08 EPSS 84.8% to 99.3%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-08-10 (past due).

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.

Official fix for CVE-2026-8037

The authoritative fix and affected-version list are published by the vendor. Find the LoadMaster advisory on Progress Security Advisories.

Common questions about CVE-2026-8037

Is CVE-2026-8037 actively exploited?

Yes. CVE-2026-8037 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-08-07, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 99%.

What is the CISA deadline and required action for CVE-2026-8037?

CISA set the federal (BOD 22-01) remediation due date at 2026-08-10, which has passed; treat any unremediated system as overdue. The verbatim 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.

What fixes CVE-2026-8037?

The authoritative fix is in the vendor advisory: see Progress Security Advisories for the patched LoadMaster versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-8037?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-8037's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.