CVE-2026-3519
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOS Command Injection Remote Code Execution Vulnerability in API in Progress ADC Products allows an authenticated attacker with “VS Administration” permissions to execute arbitrary commands on the LoadMaster appliance by exploiting unsanitized input in the 'aclcontrol' command
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUser input reaches a command interpreter without being fully separated from the command itself, so an attacker can append instructions of their own. Because those run with the application's privileges, it frequently means control of the host. The lasting fix is to avoid constructing commands from input — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.2.63.1< 7.2.63.1< 7.2.54.17< 7.2.63.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.2.54.177.2.63.1
Upgrade to LoadMaster/Connection Manager version 7.2.63.1 (or 7.2.54.17 for the 7.2.54 branch)
- 1. Identify the current LoadMaster/Connection Manager version by navigating to the web interface and checking the 'Help' > 'About' section, or via CLI using 'lmutil lmversion'
- 2. For Connection Manager For Objectscale: upgrade to version 7.2.63.1 or later
- 3. For Ecs Connection Manager: upgrade to version 7.2.63.1 or later
- 4. For LoadMaster: determine which version branch is in use (7.2.54.x or 7.2.63.x) and upgrade to the corresponding fixed release (7.2.54.17 for 7.2.54 branch, 7.2.63.1 or later for 7.2.63 branch)
- 5. Download the update from the official Progress LoadMaster support portal or the vendor patch URL provided
- 6. Apply the update via the LoadMaster web interface under 'System Configuration' > 'System Upgrade' > 'Update ADC', or via CLI using the provided upgrade mechanism
- 7. After upgrade, verify the version has been successfully applied and test that the 'aclcontrol' API endpoint properly sanitizes input
- 8. Review user permissions to ensure only necessary users retain 'VS Administration' permissions to reduce attack surface
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3519 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data