Threats / Array Networks / CVE-2025-66644
CVE-2025-66644
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Array Networks ArrayOS AG vulnerability
Array Networks ArrayOS AG contains an OS command injection vulnerability allowing arbitrary command execution on affected systems.
Verdict
Today item — known-exploited.
OS command injection in ArrayOS AG enables unauthenticated or low-privileged attackers to execute arbitrary system commands, potentially compromising device integrity and enabling lateral movement within network infrastructure.
CISA KEV Yes · 2025-12-085EPSS 0.03462 (verify live)6CVSS 7.23CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-08).
Probability (EPSS)
EPSS 0.03462 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) · Affected: Array Networks , ArrayOS AG. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious input containing shell metacharacters to break out of intended command context.
Business
Attacker gains code execution with the privileges of the vulnerable application process.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute system commands to enumerate the device configuration, installed software, and network topology.
Business
Attacker obtains detailed reconnaissance of the security appliance and connected infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence mechanisms or pivot to adjacent network segments using the compromised appliance.
Business
Security perimeter is breached; attacker gains foothold for lateral movement and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05