How severe is CVE-2009-1190?

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

Which packages are affected by CVE-2009-1190?

CVE-2009-1190 affects the following packages: org.springframework:spring-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2009-1190?

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

How do I detect CVE-2009-1190 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-2009-1190 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2009-1190 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2009-1190, including 2 in-the-wild exploitations 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-2009-1190?

CVE-2009-1190 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 87th 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-2009-1190?

CVE-2009-1190 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2009-1190 published, and has it been updated?

CVE-2009-1190 was published on May 2, 2022 and was last updated on December 7, 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-2009-1190 — spring-core

CVE-2009-1190 is a CWE-399 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 Inefficient Regular Expression Complexity

Published

May 2, 2022

Updated

Dec 7, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.springframework:spring-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

Algorithmic complexity vulnerability in the java.util.regex.Pattern.compile method in Sun Java Development Kit (JDK) before 1.6, when used with spring.jar in SpringSource Spring Framework 1.1.0 through 2.5.6 and 3.0.0.M1 through 3.0.0.M2 and dm Server 1.0.0 through 1.0.2, allows remote attackers to cause a denial of service (CPU consumption) via serializable data with a long regex string containing multiple optional groups, a related issue to CVE-2004-2540.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-core`	≥ 1.1.0&&< 3.0.0.RELEASE	3.0.0.RELEASE`org.springframework:spring-core:3.0.0.RELEASE`

Affected Products

1 product · 139 configurations

Application

jdksun

≤ 1.5.0

78 versions

1.1.01.1.61.1.7b1.1.81.2.01.2.11.2.21.3.01.3.0_011.3.0_021.3.0_031.3.0_04

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.

Algorithmic complexity vulnerability in the java.util.regex.Pattern.comp…

bugzilla.redhat.comNVDOct 2018

Report on packetstormsecurity.org

packetstormsecurity.orgNVDOct 2018

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.0.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-1190 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-1190 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works