dbcve.org
Shardingsphere UiApplication · Apache

CVE-2021-26558

HIGH · 7.5 CVSS v3.1 Published 2021-11-11
Fix available
A fix is available. Upgrade to 5.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Deserialization of Untrusted Data vulnerability of Apache ShardingSphere-UI allows an attacker to inject outer link resources. This issue affects Apache ShardingSphere-UI Apache ShardingSphere-UI version 4.1.1 and later versions; Apache ShardingSphere-UI versions prior to 5.0.0.

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

Apache ShardingSphere-UI versions 4.1.1 through versions prior to 5.0.0 contain a deserialization vulnerability where untrusted data is deserialized without proper validation, allowing attackers to inject malicious external link resources into the application.

MitigationUpgrade Apache ShardingSphere-UI to version 5.0.0 or later, which contains the fix for this vulnerability. If upgrading is not immediately possible, implement input validation and sanitization on any user-controlled data before deserialization.

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
Shardingsphere UiApplication
Affected:>= 4.1.1, < 5.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Locate ShardingSphere-UI installation
    Identify where Apache ShardingSphere-UI is deployed. Check application directories, JAR files, WAR files, or server deployment folders where the ShardingSphere-UI component is installed.
    Affected if ShardingSphere-UI is present on the system
  2. Determine installed version
    Extract or view the version information from the ShardingSphere-UI installation. This may be in the JAR/WAR manifest, a version file, pom.xml, or displayed in the application startup logs. Common locations include the archive filename, META-INF/MANIFEST.MF inside JAR files, or the application's about/version page if accessible via web UI.
    Affected if Version cannot be determined or is not visible
  3. Compare version to affected range
    Verify the installed version against the affected range: versions 4.1.1 through any version prior to 5.0.0. If the version is 4.1.1, 4.1.2, 4.x.x (where x is any number), or any 5.0.0-alpha/beta/RC release prior to stable 5.0.0, it falls within the affected range.
    Affected if Installed version is 4.1.1 or higher but lower than 5.0.0

If ShardingSphere-UI is present and the installed version falls within 4.1.1 to less than 5.0.0, the environment is vulnerable to CVE-2021-26558.

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 5.0.0 or later
Fixed in 5.0.0
Interim mitigation

Upgrade Apache ShardingSphere-UI to version 5.0.0 or later, which contains the fix for this vulnerability. If upgrading is not immediately possible, implement input validation and sanitization on any user-controlled data before deserialization.

Recommended fix High confidence

ShardingSphere-UI 5.0.0 or later (ShardingSphere 5.x)

  1. 1. Back up all current ShardingSphere-UI configurations and data
  2. 2. Stop the ShardingSphere-UI service
  3. 3. Download Apache ShardingSphere version 5.0.0 or later from the official Apache ShardingSphere release repository
  4. 4. Install version 5.0.0 or later following the standard upgrade procedure
  5. 5. Restore configurations from the backup
  6. 6. Start the ShardingSphere service
  7. 7. Verify the service is running correctly and test functionality
Caveat Version 5.x may have configuration or feature changes compared to 4.x; review migration guide for breaking changes

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

Fix this in Shardingsphere Ui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26558 — 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-2021-26558 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