# CVE-2026-40989: Self Routing guard bypassed via function composition > Attackers can cause out-of-memory errors and service disruption in Spring Cloud Function via infinite recursion in the routing layer. - **Severity:** Medium 5.7 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 1 Jun 2026 - **Updated:** 1 Jun 2026 - **Also known as:** GHSA-x9c7-5h6g-hq8q ## What is CVE-2026-40989? CVE-2026-40989 is a medium-severity denial of service vulnerability in Spring Cloud Function, published on 1 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-674 (Uncontrolled Recursion) ## Which versions are affected by CVE-2026-40989? 10 open source packages ship an affected version, including org.springframework.cloud:spring-cloud-function-context. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 3.2.10 to 3.2.15 | None | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 3.2.10 to 3.2.15 | None | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 4.1.0 to 4.1.9 | None | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 4.1.0 to 4.1.9 | None | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 4.2.0 to 4.2.5 | None | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 4.2.0 to 4.2.5 | None | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 4.3.0 | 4.3.3 | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 4.3.0 | 4.3.3 | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 5.0.0 | 5.0.2 | | `org.springframework.cloud:spring-cloud-function-context` | Maven | From 5.0.0 | 5.0.2 | Products: Vmware Spring Cloud Function. ## How do I fix CVE-2026-40989? Upgrade org.springframework.cloud:spring-cloud-function-context to a fixed version for your release line: 4.3.3 or 5.0.2. ## Is CVE-2026-40989 being exploited? There is no known exploitation of CVE-2026-40989 in the wild and no public exploit code. ## Other vulnerabilities in Spring Cloud Function - [CVE-2022-22979](https://insights.sbomify.com/CVE-2022-22979/): Denial of Service in Spring Cloud Function (high 7.5) - [CVE-2026-40990](https://insights.sbomify.com/CVE-2026-40990/): Unbounded cache for function definitions (medium 5.7) - [CVE-2026-59297](https://insights.sbomify.com/CVE-2026-59297/): Spring Cloud Function can incorrectly determine if URI is secure (low 3.1) - [CVE-2026-59298](https://insights.sbomify.com/CVE-2026-59298/): Potential for improper filtering of HTTP headers in Spring Cloud Function (low 3.1) - [CVE-2026-59299](https://insights.sbomify.com/CVE-2026-59299/): Composition lookup can potentially poison base function in Spring Cloud Function (low 3.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40989 and fix it if it is affected. What it is: CVE-2026-40989 is a medium-severity denial of service vulnerability in Spring Cloud Function, published on 1 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-40989 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 3.2.10 up to 3.2.15; no fix listed - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 3.2.10 up to 3.2.15; no fix listed - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 4.1.0 up to 4.1.9; no fix listed - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 4.1.0 up to 4.1.9; no fix listed - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 4.2.0 up to 4.2.5; no fix listed - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 4.2.0 up to 4.2.5; no fix listed - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 4.3.0; fixed in 4.3.3 - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 4.3.0; fixed in 4.3.3 - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 5.0.0; fixed in 5.0.2 - org.springframework.cloud:spring-cloud-function-context (Maven): affected from 5.0.0; fixed in 5.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40989/ (Markdown: https://insights.sbomify.com/CVE-2026-40989/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40989 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40989 - OSV: https://osv.dev/vulnerability/CVE-2026-40989 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40989/ Summaries are generated and may contain mistakes; the official description above is the record.