Spring BootFramework / library · VMware
CVE-2021-26987
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 · uneditedElement Plug-in for vCenter Server incorporates SpringBoot Framework. SpringBoot Framework versions prior to 1.3.2 are susceptible to a vulnerability which when successfully exploited could lead to Remote Code Execution. All versions of Element Plug-in for vCenter Server, Management Services versions prior to 2.17.56 and Management Node versions through 12.2 contain vulnerable versions of SpringBoot Framework.
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 · high confidenceThe Element Plug-in for vCenter Server, Management Services, and Management Node contain vulnerable SpringBoot Framework versions prior to 1.3.2, which are susceptible to remote code execution. This is a known deserialization vulnerability in older SpringBoot versions that can be exploited without authentication.
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
Spring BootFramework / library
< 1.3.2all versions< 2.17.56<= 12.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check for NetApp Element Plug-in for vCenter Server installationLook for the Element Plug-in installation directory or check vCenter Server plugins list for Element plugin presenceAffected if The plugin is installed and running (all versions are affected)
-
Determine NetApp Management Services versionRun 'msversion' command or check the Management Services UI for the installed version numberAffected if Version is lower than 2.17.56
-
Determine NetApp Solidfire or HCI Management Node versionRun '纯mnode version' or check the Management Node UI for the installed versionAffected if Version is 12.2 or lower
-
Identify SpringBoot Framework version in useCheck the bundled SpringBoot library JAR files or manifest within the affected NetApp product directories for spring-boot.version propertyAffected if SpringBoot version is below 1.3.2
You are affected if any NetApp product (Element Plug-in for vCenter, Management Services below 2.17.56, or Management Node 12.2 or lower) is running, or if the bundled SpringBoot Framework is detected at a version below 1.3.2.
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 · scoped1.3.22.17.56
Upgrade SpringBoot Framework to version 1.3.2 or later. For Management Services, upgrade to version 2.17.56 or higher. Ensure Management Nodes are updated beyond version 12.2.
Spring Boot >= 1.3.2; Management Services >= 2.17.56; Management Node > 12.2
- Upgrade Spring Boot to version 1.3.2 or later
- For Management Services for Element Software and NetApp HCI: upgrade to version 2.17.56 or later
- For SolidFire & HCI Management Node: upgrade to a version greater than 12.2 (contact NetApp for specific fixed release)
- For Element Plug-in for vCenter Server: contact NetApp for patch or upgrade path as all versions are affected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Boot
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26987 — 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-2021-26987 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