CVE-2026-22273
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 ECS, versions 3.8.1.0 through 3.8.1.7, and Dell ObjectScale versions prior to 4.2.0.0, contains an Use of Default Credentials vulnerability in the OS. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Elevation of privileges.
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 ECS (versions 3.8.1.0-3.8.1.7) and Dell ObjectScale (prior to 4.2.0.0) contain Use of Default Credentials vulnerability in the underlying operating system. A low-privileged attacker with network access to the system can exploit these default credentials to achieve privilege escalation from a standard user to administrative/root level access.
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>= 3.8.1.0, < 4.2.0.0< 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify product and versionRun 'version' or 'cat /etc/*release' command, or check the management UI for the installed Dell ECS or ObjectScale version numberAffected if Version is 3.8.1.0 through 3.8.1.7 for ECS, or any version prior to 4.2.0.0 for ObjectScale
-
List all local OS accountsRun 'cat /etc/passwd' or use 'getent passwd' to enumerate all user accounts on the systemAffected if Any unexpected or unknown accounts exist besides standard system accounts
-
Check for default or unchanged credentialsReview authentication configuration files, check if default vendor credentials (such as 'admin', 'root', or service-specific accounts) are still enabled or unmodified. Look for shadow file access patterns with 'getent shadow' and compare against known default password hashes if availableAffected if Default OS credentials have not been changed from vendor defaults, or weak/default passwords are still active for any account
-
Review sudo and group membershipRun 'getent group' and check 'sudo -l -U <username>' for each account to see privilege escalation pathsAffected if Any low-privileged user has been added to sudoers, wheel, or admin groups without documented approval
-
Audit authentication logs for suspicious accessReview /var/log/secure, /var/log/auth.log, or equivalent system logs for login events from non-standard IP addresses or after-hours activityAffected if Logins have occurred using default credentials or from unauthorized source IP addresses
-
Check network exposure of management interfacesRun 'netstat -tlnp' or 'ss -tlnp' to list listening services, and review firewall rules with 'iptables -L' or 'firewall-cmd --list-all'Affected if Administrative ports (22, 443 for management UI, or other remote access services) are bound to non-localhost and accessible from untrusted networks
You are affected if your system runs Dell ECS 3.8.1.0-3.8.1.7 or Dell ObjectScale prior to 4.2.0.0 and the default OS credentials remain unchanged or any unauthorized privileged accounts exist.
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.2.0.0
Immediately change all default OS credentials on affected systems, disable unnecessary remote access paths, restrict network exposure of administrative interfaces, and apply vendor patches to upgrade to version 4.2.0.0 or later for ObjectScale and the latest 3.8.1.x patch for ECS.
4.2.0.0 or later
- Schedule a maintenance window for the upgrade
- Back up all current configuration data and verify backup integrity
- Review Dell ECS/ObjectScale upgrade documentation for your specific version
- Upgrade Dell Elastic Cloud Storage to version 4.2.0.0 or later
- Upgrade Dell ObjectScale to version 4.2.0.0 or later
- After upgrade, change any default credentials to strong, unique passwords
- Verify the upgrade was successful and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22273 — 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-22273 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