CVE REMEDIATION GUIDE
Priority reviewCriticalFixed-version data available

CVE-2026-8037 remediation guide

Progress Software LoadMaster, ECS Connections Manager, Object Scale Connection Manager

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

Open CVE record
ProductProgress Software LoadMaster, ECS Connections Manager, Object Scale Connection Manager
Affected versions>= V7.2.60.0 < V7.2.63.2, >= V7.2.45.12 < V7.2.54.18, < 7.2.63.2, < 7.2.54.18, >= 7.2.55.0 < 7.2.63.2
Fixed versions7.2.63.2, 7.2.54.18
Priority basisPriority · CVSS 9.8 · EPSS 43.4%
01

Identify the affected asset

Confirm whether Progress Software LoadMaster, ECS Connections Manager, Object Scale Connection Manager is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= V7.2.60.0 < V7.2.63.2, >= V7.2.45.12 < V7.2.54.18, < 7.2.63.2, < 7.2.54.18, >= 7.2.55.0 < 7.2.63.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 7.2.63.2, 7.2.54.18. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.