CVE-2026-40990

Spring Cloud Function Context: Uncontrolled Recursion is possible while attempting to add infinite amount of functions to Function Registry

OOM error is possible while attempting to add infinite amount of functions to Function Registry.

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.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2026-40990 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.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-40990? CVE-2026-40990 is a medium-severity allocation of resources without limits or throttling 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. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2026-40990? CVE-2026-40990 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.
3. Which versions of org.springframework.cloud:spring-cloud-function-context are affected by CVE-2026-40990? org.springframework.cloud:spring-cloud-function-context (maven) versions >= 4.3.0, < 4.3.3 is affected.
4. Is there a fix for CVE-2026-40990? Yes. CVE-2026-40990 is fixed in 4.3.3, 5.0.2. Upgrade to this version or later.
5. Is CVE-2026-40990 exploitable, and should I be worried? Whether CVE-2026-40990 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
6. What actually determines whether CVE-2026-40990 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.
7. How do I fix CVE-2026-40990?
   • 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