CVE-2025-36601
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 · uneditedDell PowerScale OneFS, versions 9.5.0.0 through 9.11.0.0, contains an exposure of sensitive information to an unauthorized actor vulnerability. An unauthenticated remote attacker could potentially exploit this vulnerability, leading to Information disclosure.
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 confidenceDell PowerScale OneFS versions 9.5.0.0 through 9.11.0.0 contains an information disclosure vulnerability allowing unauthenticated remote attackers to access sensitive data. The specific mechanism of exposure is not detailed in available sources.
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.8.0.0, < 9.10.1.3>= 9.5.0.0, < 9.5.1.4>= 9.6.0, < 9.7.1.10= 9.11.0.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 PowerScale OneFS versionRun the command 'isi version' or 'isi_get_version' from the OneFS CLI to retrieve the currently installed firmware version.Affected if The displayed version falls within the affected ranges: 9.5.0.0 to 9.5.1.3, 9.6.0.0 to 9.7.1.9, 9.8.0.0 to 9.10.1.2, or exactly 9.11.0.0
-
Confirm OneFS management interface accessibilityVerify network exposure of OneFS management ports (default TCP 8080, 8443 for WebUI) by reviewing firewall rules or using 'isi network interfaces' to list active network configurations.Affected if The management interface is reachable from untrusted networks (such as the internet or non-segmented internal networks)
-
Review access controls on OneFS API endpointsExamine the OneFS configuration for any anonymous or unauthenticated access permissions using 'isi auth' commands or the OneFS WebUI under Access > Authentication settings.Affected if Anonymous or unauthenticated access is permitted to any API or administrative endpoints
You are affected if your PowerScale OneFS version is within the listed affected ranges AND the management interface is network-accessible without authentication.
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.5.1.49.7.1.109.10.1.3
Upgrade Dell PowerScale OneFS to a version beyond 9.11.0.0 or apply vendor-supplied patches. As an interim measure, restrict network access to the OneFS management interfaces.
Upgrade to OneFS 9.10.1.3 or later (or the latest available stable release) based on your current version branch
- 1. Identify the current PowerScale OneFS version by running 'isi version' or checking the web UI
- 2. Based on current version, determine the appropriate upgrade target: if running 9.5.0.0-9.5.1.x, upgrade to 9.5.1.4 or later; if running 9.6.0-9.7.1.x, upgrade to 9.7.1.10 or later; if running 9.8.0.0-9.10.1.x, upgrade to 9.10.1.3 or later
- 3. Review Dell PowerScale OneFS upgrade documentation and release notes for the target version
- 4. Create a backup or snapshot of the cluster before upgrading
- 5. Schedule a maintenance window as upgrades require cluster downtime
- 6. Download the upgrade ISO from Dell support portal (www.dell.com/support)
- 7. Execute the upgrade following Dell's recommended procedure, typically using 'isi upgrade' command or the web UI
- 8. Verify the upgrade was successful and the version matches the expected fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36601 — 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-36601 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