CVE-2026-54470
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 Unisphere for PowerMax, version(s) 10.3.0.5 and prior contain(s) an Improper Restriction of XML External Entity Reference vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Unauthorized access.
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 Unisphere for PowerMax versions 10.3.0.5 and prior contain an XXE (XML External Entity) vulnerability where the XML parser processes external entity references. A low-privileged remote attacker can exploit this by submitting malicious XML payloads to the Unisphere API or web interface, potentially reading internal files, performing SSRF attacks, or gaining unauthorized access to the 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< 10.3.0.7CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Confirm Dell Unisphere for PowerMax is deployedIdentify if Unisphere for PowerMax is installed in your environment by checking for the Unisphere web interface or API endpoints (typically accessible on port 8443 or 443). Review your inventory or network scans for Unisphere services.Affected if Unisphere for PowerMax is accessible on your network and responds to HTTP/HTTPS requests.
-
Determine the installed Unisphere versionLog into the Unisphere web interface and navigate to the About or Support section to view the software version. Alternatively, query the Unisphere API version endpoint if available, or check the installation documentation for your environment.Affected if The installed version is 10.3.0.5 or prior, or any version below 10.3.0.7.
-
Verify XML API endpoints are exposedReview your network configuration to determine if the Unisphere REST API or web interface (which accepts XML payloads) is accessible from network segments accessible to remote attackers. Check for exposed ports 8443, 443, or custom ports configured for Unisphere.Affected if Unisphere XML API or web interface endpoints are reachable from untrusted network segments.
-
Check XML parser configuration for external entity processingIf you have access to Unisphere configuration files or administrative controls, inspect the XML parser settings to determine whether external entity processing and DTD processing are enabled. Consult Dell Unisphere documentation for the specific configuration files or settings related to XML parsing.Affected if XML parsers are configured to allow external entity resolution or DTD processing, which is the default vulnerable state in affected versions.
-
Assess authentication controls on XML input endpointsReview user access controls and authentication requirements for Unisphere API and web interface endpoints that accept XML input. Determine if low-privileged users can submit XML payloads to these endpoints.Affected if Low-privileged or unauthenticated users can submit XML requests to Unisphere endpoints.
You are affected if Dell Unisphere for PowerMax is accessible on your network and the installed version is below 10.3.0.7, with XML parser external entity processing enabled on accessible API or web interface endpoints.
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 · scoped10.3.0.7
Upgrade to a patched version of Dell Unisphere for PowerMax that disables external entity processing in XML parsers, or configure XML parsers to disable external entities and DTD processing if a vendor patch is not immediately available.
10.3.0.7
- 1. Back up the current Unisphere for PowerMax configuration and data.
- 2. Review the Dell Unisphere for PowerMax 10.3.0.7 release notes for any prerequisites or special instructions.
- 3. Download the Unisphere for PowerMax version 10.3.0.7 from Dell's support website (support.dell.com).
- 4. Follow Dell's documented upgrade procedure for Unisphere for PowerMax, ensuring proper system downtime is scheduled.
- 5. Verify the upgrade was successful by checking the version in the Unisphere interface.
- 6. Confirm the XXE vulnerability is resolved by reviewing the security fix details in the 10.3.0.7 release notes.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54470 — 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-54470 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