CVE-2025-66644
Array Networks ArrayOS AG before 9.4.5.9 allows command injection, as exploited in the wild in August through December 2025.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.
Also consider: shlex/execve-style APIs
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-66644 being exploited?
Yes. CVE-2025-66644 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-66644?
CVE-2025-66644 is rated High with a CVSS score of 7.2. 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-2025-66644?
Not known from our data. No patch reference has been recorded for CVE-2025-66644, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-66644 affect?
CVE-2025-66644 affects arraynetworks:arrayos_ag. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 9.4.5.9
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.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 9 Dec 2025 (SSVC 2.0.3).
timeline
- 5 Dec 2025Published
- 8 Dec 2025Added to CISA KEV (exploited in the wild) · 2 days later
- 9 Dec 2025CISA SSVC assessment: exploitation active · 1 day later
- 29 Dec 2025CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 60 days (about 2 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linkjpcert.or.jp /at/2025/at250024.html
- Linkx.com /ArraySupport/status/1921373397533032590
- Linkbleepingcomputer.com /news/security/hackers-are-exploiting-arrayos-ag-vpn-flaw-to-plant-webshells/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-66644
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.