Skip to content
← Browse CVEs

CVE-2016-1000027

Critical · CVSS 9.8EPSS 32.3%CWE-502 · Deserialization of Untrusted Data

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

Published

Community ground truth

Community verdict

4 verdicts
Not a real issue

Includes TruePositive's curated baseline from public sources — community verdicts accrue on top.

to add your verdict.

Community real-world severity: High (High 1) — CVSS base score 9.8

Practitioners rate this lower than its CVSS — likely over-rated by the score.

Field notes & remediation

Verdicts are the quick signal — notes are the evidence and fixes behind them.

  • 0
    Field note · Nadia PetrovaCurated

    The textbook SCA false positive. The flaw is real only if your app actually exposes Spring's HttpInvokerServiceExporter / RemoteInvocationSerializingExporter and deserializes attacker-controlled data — a remoting style almost nobody uses today. But spring-web carries the class transitively, so dependency scanners flag every Spring app at critical regardless of whether the vulnerable endpoint exists. VMware/Spring long declined to treat it as a framework vulnerability for exactly this reason.

    Sources: NVD · Spring issue #24434.

  • 0
    Field note · Mara OkonkwoCurated

    Dissent — don't get complacent: if you do stand up a Spring HTTP Invoker endpoint (or any ObjectInputStream over untrusted bytes), this is a genuine unauth RCE. The 'false positive' verdict is for the ~99% who only carry the dependency transitively, not for the few who actually use remoting.

  • 0
    Remediation · Waleed AzizCurated

    If you don't use HTTP Invoker remoting (almost certainly), suppress/accept the finding with a documented justification — don't burn a sprint on it. If you do, drop the exporter or migrate off Java serialization; Spring 6 removed the legacy remoting support entirely.

Same weaknessCWE-502 · Deserialization of Untrusted Data.