CVE-2026-28261
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 Elastic Cloud Storage, version 3.8.1.7 and prior, and Dell ObjectScale, versions prior to 4.1.0.3 and version 4.2.0.0, contains an Insertion of Sensitive Information into Log File vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to secret exposure. The attacker may be able to use the exposed secret to access the vulnerable system with privileges of the compromised account.
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 confidenceThis vulnerability allows a low-privileged local attacker to access log files containing sensitive information (secrets) on Dell Elastic Cloud Storage and ObjectScale systems. The attacker can read these logs to extract exposed credentials and use them to gain elevated privileges on the affected system.
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< 4.2.0.1< 4.1.0.3= 4.2.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
- 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 Dell product and versionRun the product-specific version command or check the installation manifest. For ECS, typically use 'esrs_ctl --version' or check /opt/emc/ecs/version. For ObjectScale, check the deployment configuration or run 'objectscale version'.Affected if The installed version is Dell Elastic Cloud Storage < 4.2.0.1 OR Dell ObjectScale < 4.1.0.3 OR = 4.2.0.0
-
Locate log directories for Dell ECS or ObjectScaleIdentify the default log paths. Common locations include /var/log/ecs, /var/log/objectscale, or the configured log directory specified in the product's logging configuration file.Affected if Log files exist and are readable by low-privileged users
-
Search log files for exposed credentials or secretsUse grep or similar tools to search log files for patterns indicating sensitive data: look for strings like 'password', 'secret', 'token', 'key', 'api_key', 'access_key', or base64-encoded values that resemble credentials.Affected if Log files contain any plaintext or weakly obfuscated credentials, tokens, or secrets
-
Review logging configuration for sensitive data handlingExamine the logging configuration files (e.g., logback.xml, log4j.xml, or product-specific config) to determine if sensitive parameters are being logged, and check if log verbosity is set to DEBUG or TRACE which may expose additional data.Affected if Configuration allows logging of authentication parameters, API keys, tokens, or other secrets
-
Verify access controls on log filesCheck file permissions on log directories and files to confirm whether low-privileged local users have read access. Use 'ls -la' on log directories and examine group/world read permissions.Affected if Log files are readable by non-admin users or the 'others' group
You are affected if your Dell Elastic Cloud Storage version is below 4.2.0.1 or ObjectScale version is below 4.1.0.3 (or equals 4.2.0.0) AND log files contain exposed credentials or are readable by low-privileged users.
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 · scoped4.1.0.34.2.0.1
Audit all code paths that write to log files to identify where sensitive information is being logged, implement proper sanitization or masking of secrets before logging, and rotate any existing logs that may contain exposed secrets.
Elastic Cloud Storage: 4.2.0.1 | ObjectScale: 4.1.0.3
- Identify which Dell product is in use: Elastic Cloud Storage or ObjectScale
- For Elastic Cloud Storage users: Upgrade to version 4.2.0.1 or later
- For ObjectScale users: Upgrade to version 4.1.0.3 or later (avoid version 4.2.0.0)
- After upgrading, review log files to ensure no sensitive information was previously exposed
- Verify the upgrade was successful by confirming the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28261 — 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-28261 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