# Spring Framework Inefficient Regular Expression Complexity

Advisory record · `GHSA-wjjr-h4wh-w6vv`

- **Identifiers:** `GHSA-wjjr-h4wh-w6vv` · `CVE-2009-1190`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-1333](https://cwe.mitre.org/data/definitions/1333.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 2 May 2022
- **Updated:** 7 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 May 2022, 03:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.springframework:spring-core` (Maven): affected `>=1.1.0, <3.0.0.RELEASE`; fixed in `3.0.0.RELEASE`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Spring Framework spring-core versions 1.1.0 up to 3.0.0.RELEASE are affected. When used with Sun JDK versions before 1.6, a remote attacker can send serializable data containing a long regex string with multiple optional groups, causing high CPU consumption and denial of service. Upgrade to spring-core 3.0.0.RELEASE or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.028, the 86th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wjjr-h4wh-w6vv)

## Sources

- [GitHub Advisory Database: GHSA-wjjr-h4wh-w6vv](https://github.com/advisories/GHSA-wjjr-h4wh-w6vv)
- [OSV: GHSA-wjjr-h4wh-w6vv](https://osv.dev/vulnerability/GHSA-wjjr-h4wh-w6vv)
- <https://nvd.nist.gov/vuln/detail/CVE-2009-1190>
- <https://bugzilla.redhat.com/show_bug.cgi?id=497161>
- <https://exchange.xforce.ibmcloud.com/vulnerabilities/50083>
- <http://www.packetstormsecurity.org/hitb06/DAY_1_-_Marc_Schoenefeld_-_Pentesting_Java_J2EE.pdf>
- <http://www.springsource.com/securityadvisory>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wjjr-h4wh-w6vv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wjjr-h4wh-w6vv/>. Everything for agents: <https://agentprime.io/llms.txt>.
