How severe is CVE-2011-2894?

No CVSS score has been assigned to CVE-2011-2894 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-2894?

CVE-2011-2894 affects the following packages: org.springframework:spring-core (Maven), org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-2894?

Update org.springframework:spring-core to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2894 is resolved across your whole dependency graph.

How do I detect CVE-2011-2894 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-2894 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2011-2894 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2011-2894, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-2894?

CVE-2011-2894 has an EPSS (Exploit Prediction Scoring System) score of 8.6%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-2894?

CVE-2011-2894 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2011-2894 published, and has it been updated?

CVE-2011-2894 was published on May 14, 2022 and was last updated on December 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2011-2894 — spring-core

Fix: spring-projects/spring-framework@070a723

CVE-2011-2894 is a Deserialization of Untrusted Data vulnerability in org.springframework:spring-core. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.springframework:spring-core — see the affected versions and patch details below.

Spring Framework and Spring Security vulnerable to Deserialization of Untrusted Data

Published

May 14, 2022

Updated

Dec 3, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

8.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.springframework:spring-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize objects from untrusted sources, which allows remote attackers to bypass intended security restrictions and execute untrusted code by (1) serializing a java.lang.Proxy instance and using InvocationHandler, or (2) accessing internal AOP interfaces, as demonstrated using deserialization of a DefaultListableBeanFactory instance to execute arbitrary commands via the java.lang.Runtime class.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-core`	≥ 3.0.0&&< 3.0.6	3.0.6`org.springframework:spring-core:3.0.6`
☕Maven	`org.springframework.security:spring-security-core`	≥ 3.0.0&&< 3.0.6	3.0.6`org.springframework.security:spring-security-core:3.0.6`
☕Maven	`org.springframework.security:spring-security-core`	≥ 2.0.0&&< 2.0.7	2.0.7`org.springframework.security:spring-security-core:2.0.7`

Affected Products

2 products · 2 configurations

Application

spring frameworkvmware

≥ 3.0.0 && ≤ 3.0.5

range

Application

spring securityvmware

≥ 2.0.0 && ≤ 2.0.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.…

github.comGithubJul 2013

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-core to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2894 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

RHSA-2011:1334Red Hat JBoss SOA Platform 5.1

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-2894 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works