CVE-2026-40989 is a medium-severity (CVSS 5.7) CWE-674 vulnerability in org.springframework.cloud:spring-cloud-function-context. A fix is available for org.springframework.cloud:spring-cloud-function-context — see the affected versions and patch details below.
Self Routing guard bypassed via function composition
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40989.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-40989 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-contextReal-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
Under infinite recursion in the routing layer, request-handling can cause OOM error.
Affected Spring Products and Versions: Spring Cloud Function 3.2.x: versions prior to 3.2.16 Spring Cloud Function 4.1.x: versions prior to 4.1.10 Spring Cloud Function 4.2.x: versions prior to 4.2.6 Spring Cloud Function 4.3.x: versions prior to 4.3.3 Spring Cloud Function 5.0.x: versions prior to 5.0.2 Older, unsupported versions are also affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.cloud:spring-cloud-function-context | ≥ 4.3.0&&< 4.3.3 | 4.3.3org.springframework.cloud:spring-cloud-function-context:4.3.3 |
| ☕Maven | org.springframework.cloud:spring-cloud-function-context | ≥ 5.0.0&&< 5.0.2 | 5.0.2org.springframework.cloud:spring-cloud-function-context:5.0.2 |
| ☕Maven | org.springframework.cloud:spring-cloud-function-context | ≥ 3.2.10 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-function-context | ≥ 4.1.0 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-function-context | ≥ 4.2.0 | No fix |
Affected Products
spring cloud functionvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-function-context, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.cloud:spring-cloud-function-context to 4.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40989 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-40989 in your dependencies?
Find it across Maven, including transitive dependencies.