dbcve.org
Elastic Cloud StorageApplication · Dell

CVE-2026-22276

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-23
Fix available
A fix is available. Upgrade to 4.2.0.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Dell ECS, versions 3.8.1.0 through 3.8.1.7, and Dell ObjectScale versions prior to 4.2.0.0, contains a Cleartext Storage of Sensitive Information 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 confidence

Dell ECS (versions 3.8.1.0-3.8.1.7) and ObjectScale (prior to 4.2.0.0) store sensitive information in cleartext, allowing a low-privileged local attacker to access unencrypted sensitive data that should be protected.

MitigationEnable encryption at rest for stored sensitive data, rotate any exposed credentials, and apply vendor patches to upgrade to ObjectScale 4.2.0.0 or later.

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
Elastic Cloud StorageApplication
Affected:>= 3.8.1.0, < 4.2.0.0
ObjectscaleApplication
Affected:< 4.2.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Run 'ecs-cluster --version' for ECS or 'objectscale --version' for ObjectScale, or check the product's About/Support page in the management console
    Affected if The version is 3.8.1.0 through 3.8.1.7 for ECS, or below 4.2.0.0 for ObjectScale
  2. Check encryption at rest status
    Access the storage cluster configuration settings via the management UI or CLI command 'ecs-cluster config get encryption.at.rest' (or equivalent ObjectScale command)
    Affected if Encryption at rest is disabled or not configured for the storage system
  3. Locate sensitive data storage locations
    Review the ECS or ObjectScale data directories and configuration files for stored credentials, keys, or other sensitive data using file system inspection commands
    Affected if Cleartext sensitive files (credentials, keys, tokens) are found in unprotected storage locations
  4. Verify user access controls
    Check file and directory permissions on sensitive data storage paths using 'ls -la' or equivalent commands to confirm if low-privileged users can read these files
    Affected if Low-privileged local users have read access to files containing unencrypted sensitive data

A system is affected if it runs Dell ECS 3.8.1.0-3.8.1.7 or ObjectScale below 4.2.0.0 and has encryption at rest disabled, exposing cleartext sensitive data accessible to low-privileged local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.2.0.0 or later
Fixed in 4.2.0.0
Interim mitigation

Enable encryption at rest for stored sensitive data, rotate any exposed credentials, and apply vendor patches to upgrade to ObjectScale 4.2.0.0 or later.

Recommended fix High confidence

Upgrade to Dell ECS or ObjectScale version 4.2.0.0 or later

  1. 1. Identify the current installed version of Dell Elastic Cloud Storage (ECS) or ObjectScale using the system management interface or CLI
  2. 2. Review the Dell ECS or ObjectScale upgrade documentation for the 4.2.0.0 release to understand prerequisites and compatibility requirements
  3. 3. Create a complete backup of all sensitive data and system configurations before proceeding with the upgrade
  4. 4. Plan for a maintenance window as the upgrade may require system downtime
  5. 5. Follow the documented upgrade procedure to upgrade to version 4.2.0.0 or later
  6. 6. After upgrade completion, verify that the system is functioning correctly and that sensitive data is no longer stored in cleartext
  7. 7. Confirm the new version by checking the system management interface or CLI
Caveat Review Dell upgrade documentation for any breaking changes or migration requirements between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Elastic Cloud Storage Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22276 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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