CVE-2026-40633
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.10.1.7, versions 9.11.0.0 through 9.13.0.2 contains an Insertion of Sensitive Information into Log File vulnerability. A low privileged attacker with local access 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 contains a vulnerability where sensitive information is being written to log files. A low-privileged local attacker with access to the system could potentially read these logs to obtain sensitive information that should not be exposed.
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.5.0.0, < 9.10.1.8>= 9.11.0.0, < 9.13.1.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 the installed PowerScale OneFS versionUse the OneFS CLI command 'isi version' or check the System > Settings > About page in the OneFS web interface to retrieve the exact version numberAffected if The installed version falls within the affected ranges: >= 9.5.0.0 and < 9.10.1.8, or >= 9.11.0.0 and < 9.13.1.0
-
Locate and review OneFS log directoriesAccess the default log directories on the OneFS cluster (typically under /var/log/ or accessible via the OneFS CLI 'isi log' commands) and identify log files generated by the OneFS applicationAffected if Log files exist and contain unredacted sensitive information such as credentials, API keys, tokens, or personal data that should not be exposed
-
Check for sensitive data in recent log entriesSearch recent log files for patterns that may indicate sensitive information (such as password strings, authentication tokens, or user credentials) using grep or similar search tools on the log filesAffected if Sensitive information that should be redacted appears in plain text within log files
A user is affected if they are running a vulnerable OneFS version AND have sensitive data being written to accessible log files on their system.
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.10.1.89.13.1.0
Implement proper sanitization or redaction of sensitive information before logging. Review all logging paths in the OneFS application to identify and fix locations where sensitive data may be written to log files.
9.10.1.8 or later for 9.5.x-9.10.x branches; 9.13.1.0 or later for 9.11.x-9.13.x branches
- 1. Determine current OneFS version by running 'isi version' or checking the web admin console
- 2. Identify the appropriate upgrade path based on your current version (9.5.x -> 9.10.1.x or 9.11.x -> 9.13.x)
- 3. Review Dell PowerScale OneFS upgrade documentation for your current version at www.dell.com/support
- 4. Create a backup of critical data and configuration before upgrading
- 5. Schedule a maintenance window as upgrades require cluster downtime
- 6. Download the fixed OneFS image (9.10.1.8 or later for 9.5.x-9.10.x, or 9.13.1.0 or later for 9.11.x-9.13.x) from Dell support portal
- 7. Follow Dell's standard OneFS upgrade procedure using 'isi upgrade' or the web admin interface
- 8. After upgrade, verify the version matches the fixed release and confirm system functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40633 — 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-40633 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