Skip to content
Fencer Intel
critical 9.8

CVE-2016-1000027 in the critical feed json

Pivotal Spring Framework contains unsafe Java deserialization methods

published 2020-01-02 6 y ago modified 2026-10-07 33 d ago also GHSA-4wrc-f8pq-fpqp , EUVD-2022-2463

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
33.2%
EPSS 33.2% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework:spring-web 6.0.0
  • vmware spring_framework 6.0.0
  • libspring-java Debian 14, Debian 13, Debian 12 4.2.7-1

debian advisories DEBIAN-CVE-2016-1000027

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-1000027 updated cvss 9.8

spring: HttpInvokerServiceExporter readRemoteInvocation method untrusted java deserialization

  • Red Hat OpenShift Developer Tools and Services jenkins Red Hat Enterprise Virtualization 3 rhevm-dependencies, jasperreports-server-pro, redhat-support-plugin-rhev Red Hat Fuse 7 springframework springframework Red Hat JBoss Fuse 6 springframework springframework Red Hat OpenShift Container Platform 3.11 jenkins Red Hat OpenShift Container Platform 4 jenkins
    +1 more products
    Red Hat OpenShift Enterprise 2 spring-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
33 d ago

Exploit prediction

33.18% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • tenable.com https://www.tenable.com/security/research/tra-2016-20 referenced PoC, tagged "exploit" by a source, unverified
  • raw.githubusercontent.com https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000027.json referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework:spring-web
<6.0.0
6.0.0

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.