CVE-2026-23825
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 · uneditedVulnerabilities exist in a protocol-handling component of AOS-8 and AOS-10 Operating Systems. An unauthenticated attacker could exploit these vulnerabilities by sending specially crafted network messages to the affected service. Due to insufficient input validation, successful exploitation may terminate a critical system process, resulting in a denial-of-service condition.
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 · moderate confidenceA vulnerability in the protocol-handling component of Aruba AOS-8 and AOS-10 allows unauthenticated attackers to send specially crafted network messages that trigger insufficient input validation, causing termination of a critical system process and resulting in denial of service.
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>= 6.5.4.0, < 8.10.0.22>= 8.11.0.0, < 8.12.0.7>= 8.13.0.0, < 8.13.1.2>= 10.4.0.0, < 10.4.1.11>= 10.5.0.0, < 10.7.2.3>= 8.6.0.4-2.2.0.0, <= 8.6.0.4-2.2.0.7>= 8.7.0.0-2.3.0.0, <= 8.7.0.0-2.3.0.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed ArubaOS versionExecute `show version` or `show system info` on the Aruba controller CLI to retrieve the running firmware versionAffected if The displayed version falls within any of these ranges: AOS-8: >= 6.5.4.0 to < 8.10.0.22, >= 8.11.0.0 to < 8.12.0.7, >= 8.13.0.0 to < 8.13.1.2; AOS-10: >= 10.4.0.0 to < 10.4.1.11, >= 10.5.0.0 to < 10.7.2.3; SD-WAN: 8.6.0.4-2.2.0.0 through 8.6.0.4-2.2.0.7, or 8.7.0.0-2.3.0.0 through 8.7.0.0-2.3.0.9
-
Confirm the device model and software typeRun `show inventory` or `show controller-info` to verify whether the device runs ArubaOS (AOS-8 or AOS-10) or SD-WAN softwareAffected if The device runs ArubaOS or SD-WAN firmware matching the affected version ranges identified in step 1
-
Determine if protocol-handling services are activeReview `show services` or `show ip interface brief` to confirm that protocol-handling components (such as management, control plane, or routing protocols) are enabled and listening on network interfacesAffected if Protocol-handling services are enabled and the device is reachable over the network on management or control plane ports
Your environment is affected if the installed ArubaOS or SD-WAN version falls within any of the affected version ranges AND the protocol-handling component is active and accessible on the network.
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 · scoped8.10.0.228.12.0.78.13.1.2
Apply vendor patches when available; until then, restrict network access to affected services via firewall rules or access controls to limit exposure to untrusted networks.
ArubaOS: upgrade to 8.10.0.22+ (8.10.x), 8.12.0.7+ (8.11.x), 8.13.1.2+ (8.13.x), or 10.4.1.11+ (10.4.x) | SD-WAN: upgrade to latest available version beyond the vulnerable ranges
- 1. Identify the currently installed ArubaOS or SD-WAN version by running 'show version' on the controller CLI
- 2. For ArubaOS 6.5.4.0 through 8.10.x: upgrade to version 8.10.0.22 or later
- 3. For ArubaOS 8.11.x: upgrade to version 8.12.0.7 or later
- 4. For ArubaOS 8.13.x: upgrade to version 8.13.1.2 or later
- 5. For ArubaOS 10.4.x: upgrade to version 10.4.1.11 or later
- 6. For SD-WAN 8.6.0.4-2.2.x: upgrade to a version newer than 8.6.0.4-2.2.0.7
- 7. For SD-WAN 8.7.0.0-2.3.x: upgrade to a version newer than 8.7.0.0-2.3.0.9
- 8. Schedule upgrade during a maintenance window as upgrades may require controller reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23825 — 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-23825 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