CVE-2016-1000027 — Deserialization of Untrusted Data in Vmware Spring Framework
Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 33.2% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Vmware Spring Framework).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Vmware | Spring Framework | < 6.0.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 2.0 | High | 10.0 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 33.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor serialized objects in requests and unexpected processes spawned by the runtime.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- CVSS changed · 9.8
- Source status changed · → Modified
- Record created in this database
- 2020
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- github.com/spring-projects/spring-framework/issues/24434
- spring.io/blog/2022/05/11/spring-framework-5-3-20-and-5-2-22-available-now
- raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-100002
- www.tenable.com/security/research/tra-2016-20
- security.netapp.com/advisory/ntap-20230420-0009/
- bugzilla.redhat.com/show_bug.cgi
- security-tracker.debian.org/tracker/CVE-2016-1000027
- github.com/spring-projects/spring-framework/issues/24434
- github.com/spring-projects/spring-framework/issues/24434
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-41855 Spring Framework Unsafe Deserialization via Jackson JMS Converters Jun 9, 2026
- High CVE-2026-41849 Spring Framework Denial of Service via Integer Overflow in SpEL Expressions Jun 9, 2026
- High CVE-2026-41850 Spring Framework Algorithmic Denial of Service via SpEL Expressions Jun 9, 2026
- High CVE-2026-41851 Spring Framework Denial of Service via Unbounded Cache in SpEL Jun 9, 2026
- Medium CVE-2026-41853 Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux Jun 9, 2026
- Medium CVE-2026-41852 Spring Framework Arbitrary Method Invocation in SpEL Expressions Jun 9, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2016-1000027 is "Deserialization of Untrusted Data in Vmware Spring Framework", rated Critical. It affects Spring Framework (Vmware); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 33.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.