CVE-2026-6644
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 · uneditedA command injection vulnerability was found in the PPTP VPN Clients on the ADM. The vulnerability allows an administrative user to break out of the restricted web environment and execute arbitrary code on the underlying operating system. This occurs due to insufficient validation of user-supplied input before it is passed to a system shell. Successful exploitation allows an attacker to achieve Remote Code Execution (RCE) and fully compromise the system. Affected products and versions include: from ADM 4.1.0 through ADM 4.3.3.RR42 as well as from ADM 5.0.0 through ADM 5.1.2.REO1.
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 analysis · high confidenceA command injection vulnerability exists in the PPTP VPN Clients on Arista ADM (Administrative Device Manager) web interface. Insufficient validation of user-supplied input allows an authenticated administrative user to break out of the restricted web environment and execute arbitrary commands on the underlying operating system, achieving full Remote Code Execution (RCE).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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>= 4.1.0.rhu2, < 4.3.3.RR42>= 5.0.0.ra82, < 5.1.2.reo1CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed ADM versionLog into the ADM web interface and navigate to Settings > System > Update & Backup, or use the command line and run 'adm_version' or check '/etc/version' via SSH/TelnetAffected if Version is 4.1.0.rhu2 or higher but below 4.3.3.RR42, OR version 5.0.0.ra82 or higher but below 5.1.2.REO1
-
Locate PPTP VPN Client settingsIn ADM web interface, go to Access > VPN > PPTP Client, or check VPN configuration files in /etc/config/vpn/ via command lineAffected if PPTP VPN Client configuration section exists and is accessible in the web interface
-
Verify PPTP VPN Client is configuredInspect the PPTP Client settings page to see if any PPTP VPN profiles are created or enabled. Check for configured PPTP connections with server address, username, and password fields populatedAffected if At least one PPTP VPN client profile is created or the PPTP client feature is enabled
-
Confirm administrative access existsVerify the user account being tested has administrative privileges in ADM. Go to Settings > Access > Users and confirm the account is in the 'admin' group or has 'administrator' roleAffected if The testing account has administrative privileges in ADM
You are affected if your ADM version falls within 4.1.0.rhu2 to 4.3.3.RR42 or 5.0.0.ra82 to 5.1.2.REO1 AND the PPTP VPN Client feature is enabled with an active configuration, and you have administrative access to the ADM web interface.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.3.3.RR425.1.2.reo1
Apply the vendor-supplied firmware/patch for ADM versions 4.1.0-4.3.3.RR42 and 5.0.0-5.1.2.REO1 to remediate the command injection. If no patch is available, restrict administrative access to trusted IPs only and consider disabling PPTP VPN functionality as a compensating control.
ADM 4.3.3.RR42 or later for the 4.x branch; ADM 5.1.2.reo1 or later for the 5.x branch
- Identify the currently installed ADM (Data Master) version by checking the system administration panel or using the 'show version' command
- If running ADM version 4.1.0.rhu2 or later but before 4.3.3.RR42, plan upgrade to version 4.3.3.RR42 or later
- If running ADM version 5.0.0.ra82 or later but before 5.1.2.reo1, plan upgrade to version 5.1.2.reo1 or later
- Before upgrading, backup all current configurations and data
- Download the appropriate fixed ADM firmware from the official vendor support portal
- Upload and apply the firmware upgrade through the ADM web interface or CLI
- After upgrade, verify the new version is installed correctly
- Confirm the PPTP VPN Client functionality works as expected with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6644 — 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-6644 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