CVE-2025-37136
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 · uneditedArbitrary file deletion vulnerabilities have been identified in the command-line interface of an AOS-8 Controller/Mobility Conductor. Successful exploitation of these vulnerabilities could allow an authenticated remote malicious actor to delete arbitrary files within the affected system.
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 confidenceAuthenticated arbitrary file deletion vulnerability in the AOS-8 Controller/Mobility Conductor CLI. An authenticated remote attacker can execute CLI commands to delete arbitrary files on the affected system, potentially leading to denial of service or configuration tampering.
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>= 8.10.0.0, < 8.10.0.19>= 8.12.0.0, < 8.12.0.6>= 8.13.0.0, < 8.13.1.0>= 10.4.0.0, < 10.4.1.9>= 10.7.0.0, < 10.7.2.1CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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.
-
Check the ArubaOS versionLog into the CLI and execute 'show version' or access the WebUI dashboard to view the software versionAffected if The displayed version falls within one of these ranges: 8.10.0.0-8.10.0.18, 8.12.0.0-8.12.0.5, 8.13.0.0-8.13.0.x (pre-8.13.1.0), 10.4.0.0-10.4.1.8, or 10.7.0.0-10.7.2.0
-
Verify CLI authentication is enabledConfirm that CLI access is permitted for administrative accounts by checking 'show ip ssh' or reviewing user authentication settings in the configurationAffected if CLI access is enabled and accessible to any authenticated user (this is the default configuration)
-
Review CLI command logs for file deletion activityExecute 'show log system' or 'show audit' to inspect logs for unusual file deletion commands such as 'delete file' or 'rm' operations on unexpected pathsAffected if Logs contain file deletion commands executed by users who should not have needed to delete system files, or deletion of files outside normal operational scope
You are affected if your ArubaOS version is within any of the affected ranges AND CLI access is available to authenticated users, since the vulnerability allows any authenticated user to delete arbitrary files via CLI commands.
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.198.12.0.68.13.1.0
Apply vendor-supplied patches for AOS-8 when available; restrict CLI access to trusted administrative accounts and implement network segmentation to limit exposure.
ArubaOS 8.10.0.19, 8.12.0.6, 8.13.1.0, or 10.4.1.9 depending on your current branch
- 1. Identify the current ArubaOS version by running 'show version' on the controller CLI
- 2. Navigate to the HPE/Aruba support portal (support.hpe.com) and locate the software download section for ArubaOS
- 3. Download the appropriate fixed version based on your current branch: for 8.10.x download 8.10.0.19, for 8.12.x download 8.12.0.6, for 8.13.x download 8.13.1.0, for 10.4.x download 10.4.1.9
- 4. Transfer the firmware file to the controller using methods such as SCP, FTP, or the WebUI file upload
- 5. Execute the upgrade via CLI command 'upgrade-software' or via the WebUI under Maintenance > Controller > Upgrade
- 6. After the controller reboots, verify the new version with 'show version' and confirm the vulnerability is resolved
- 7. Test that legitimate file operations work properly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-37136 — 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-37136 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