CVE-2025-66644
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 · uneditedArray Networks ArrayOS AG before 9.4.5.9 allows command injection, as exploited in the wild in August through December 2025.
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 confidenceArray Networks ArrayOS AG before version 9.4.5.9 contains a command injection vulnerability allowing unauthenticated attackers to execute arbitrary commands on the underlying operating system. This critical flaw in the application gateway product has been actively exploited in the wild between August and December 2025, indicating active threat actor interest.
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< 9.4.5.9CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 ArrayOS AG versionAccess the management console or CLI and run 'show system info' or 'show version' to retrieve the firmware versionAffected if The displayed version is below 9.4.5.9
-
Verify web management interface accessibilityCheck if the ArrayOS AG web interface (HTTPS port 443 or configured management port) is reachable from network segments outside the trusted management networkAffected if The management web interface is exposed to untrusted networks
-
Confirm API endpoint exposureInspect firewall rules or network access lists to determine if API endpoints on the device are accessible from outside the trusted management networkAffected if API endpoints are reachable from untrusted networks without additional authentication barriers
-
Review authentication configurationCheck whether the default admin account or weak credentials are in use, and verify if multi-factor authentication is enabled for management loginsAffected if Default credentials are active or MFA is not enforced for administrative access
The environment is affected if ArrayOS AG version is below 9.4.5.9 AND the management web interface or API endpoints are accessible from untrusted networks.
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 · scoped9.4.5.9
Upgrade ArrayOS AG to version 9.4.5.9 or later to remediate the command injection vulnerability. Given active exploitation, prioritize patching immediately and monitor for indicators of compromise.
9.4.5.9
- 1. Identify the current version of Array Networks ArrayOS AG installed in your environment
- 2. If the current version is below 9.4.5.9, plan for an upgrade to version 9.4.5.9 or later
- 3. Review Array Networks official upgrade documentation for the specific upgrade procedure
- 4. Perform the upgrade during a scheduled maintenance window
- 5. After upgrade, verify the new version is 9.4.5.9 or higher
- 6. Confirm the command injection vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66644 — 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-2025-66644 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