Skip to content
Web

CVE-2026-3517

8.4
High
EPSS 18%Patch availableApr 20, 2026

RCE via API input in Progress ADC LoadMaster (addcountry) for Geo Admin.

common questions

Is CVE-2026-3517 being exploited?

Not confirmed. CVE-2026-3517 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 18% probability of exploitation in the next 30 days.

How severe is CVE-2026-3517?

CVE-2026-3517 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-3517?

Yes. A fix has been recorded for CVE-2026-3517. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-3517 affect?

CVE-2026-3517 affects Progress LoadMaster ADC appliances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-3517?

Patch when available; restrict API access; review Geo Admin roles

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Progress LoadMaster ADC appliances
impact

Authenticated Geo Admin can execute arbitrary commands on the LoadMaster appliance via unsanitized addcountry API input.

action required

Patch when possible

affected versions
Progress Software ECS Connections Manager
  • affected>= 7.2.49.0 and < V7.2.63.0
Progress Software LoadMaster
  • affected>= 7.1.32.0 and < V7.2.63.0
Progress Software MOVEit WAF
  • affected>= 7.2.62.0 and < V7.2.63.0
Progress Software Object Scale Connection Manager
  • affected>= 7.2.62.0 and < V7.2.63.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free