How severe is CVE-2026-40989?

CVE-2026-40989 has a CVSS score of 5.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Is there a fix for CVE-2026-40989?

Yes. CVE-2026-40989 is fixed in 4.3.3, 5.0.2. Upgrade to this version or later.

Is CVE-2026-40989 exploitable, and should I be worried?

Whether CVE-2026-40989 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-40989 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-40989

Q: What is CVE-2026-40989?

CVE-2026-40989 is a medium-severity security vulnerability in org.springframework.cloud:spring-cloud-function-context (maven), affecting versions >= 4.3.0, < 4.3.3. It is fixed in 4.3.3, 5.0.2.

Q: Which versions of org.springframework.cloud:spring-cloud-function-context are affected by CVE-2026-40989?

org.springframework.cloud:spring-cloud-function-context (maven) versions >= 4.3.0, < 4.3.3 is affected.

Q: How do I fix CVE-2026-40989?

Upgrade: org.springframework.cloud:spring-cloud-function-context to 4.3.3 or later, org.springframework.cloud:spring-cloud-function-context to 5.0.2 or later.

Summary

Spring Cloud Function Context has Uncontrolled Recursion

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.

Impact

CVE-2026-40989 has a CVSS score of 5.7 (Medium). The vector is requires physical access, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.3.3, 5.0.2); upgrading removes the vulnerable code path.

Affected versions

org.springframework.cloud:spring-cloud-function-context (>= 4.3.0, < 4.3.3) org.springframework.cloud:spring-cloud-function-context (>= 5.0.0, < 5.0.2) org.springframework.cloud:spring-cloud-function-context (>= 3.2.10, <= 3.2.15) org.springframework.cloud:spring-cloud-function-context (>= 4.1.0, <= 4.1.9) org.springframework.cloud:spring-cloud-function-context (>= 4.2.0, <= 4.2.5)

Security releases

org.springframework.cloud:spring-cloud-function-context → 4.3.3 (maven) org.springframework.cloud:spring-cloud-function-context → 5.0.2 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.springframework.cloud:spring-cloud-function-context to 4.3.3 or later; org.springframework.cloud:spring-cloud-function-context to 5.0.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-40989? CVE-2026-40989 is a medium-severity security vulnerability in org.springframework.cloud:spring-cloud-function-context (maven), affecting versions >= 4.3.0, < 4.3.3. It is fixed in 4.3.3, 5.0.2.
How severe is CVE-2026-40989? CVE-2026-40989 has a CVSS score of 5.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.springframework.cloud:spring-cloud-function-context are affected by CVE-2026-40989? org.springframework.cloud:spring-cloud-function-context (maven) versions >= 4.3.0, < 4.3.3 is affected.
Is there a fix for CVE-2026-40989? Yes. CVE-2026-40989 is fixed in 4.3.3, 5.0.2. Upgrade to this version or later.
Is CVE-2026-40989 exploitable, and should I be worried? Whether CVE-2026-40989 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-40989 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-40989?
- Upgrade org.springframework.cloud:spring-cloud-function-context to 4.3.3 or later
- Upgrade org.springframework.cloud:spring-cloud-function-context to 5.0.2 or later

Other vulnerabilities in org.springframework.cloud:spring-cloud-function-context

CVE-IDSeverityPackage summary

CVE-2026-40990Mediumorg.springframework.cloud:spring-cloud-function-context: Spring Cloud Function Context: Uncontrolled Recursion is possible while attempting to add infinite amount of functions to Function Registry CVE-2024-22271Highorg.springframework.cloud:spring-cloud-function-context: Spring Cloud Function Framework vulnerable to Denial of Service CVE-2022-22963Criticalorg.springframework.cloud:spring-cloud-function-context: Spring Cloud Function Code Injection with a specially crafted SpEL as a routing expression