dbcve.org
Spring Cloud FunctionFramework / library · VMware

CVE-2026-40989

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to 3.2.16 / 4.1.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Under infinite recursion in Spring Cloud Function's routing layer, specially crafted requests can cause the application to enter an infinite recursion loop during request handling, consuming excessive memory until an OOM error occurs, resulting in denial of service.

MitigationUpgrade Spring Cloud Function to version 3.2.16, 4.1.10, 4.2.6, 4.3.3, 5.0.2 or later to receive the patch that addresses the recursive routing vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Cloud FunctionFramework / library
Affected:>= 3.2.0, < 3.2.16>= 4.1.0, < 4.1.10>= 4.2.0, < 4.2.6>= 4.3.0, < 4.3.3>= 5.0.0, < 5.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Spring Cloud Function version
    Inspect your project's dependency management file (pom.xml, build.gradle, or gradle.lock) for the spring-cloud-function-core dependency version, or examine the MANIFEST.MF file inside the spring-cloud-function-core JAR in your runtime classpath
    Affected if The version falls within any of these ranges: >= 3.2.0 and < 3.2.16, >= 4.1.0 and < 4.1.10, >= 4.2.0 and < 4.2.6, >= 4.3.0 and < 4.3.3, or >= 5.0.0 and < 5.0.2
  2. Verify routing functionality is enabled
    Check your application configuration (application.properties or application.yml) for the property spring.cloud.function.routing or spring.cloud.function.always-route-to, or any explicit FunctionRegistration bean definitions that configure routing behavior
    Affected if Routing is explicitly enabled or function routing is configured in your Spring Cloud Function application
  3. Confirm the application exposes HTTP endpoints
    Verify that spring-cloud-function-web or spring-cloud-function-router dependencies are present in your runtime, or check if the application has servlet mappings (such as /functionRouter/** or /**) that expose functions over HTTP
    Affected if Your Spring Cloud Function application exposes functions as HTTP endpoints accessible to clients

You are affected if your application runs a Spring Cloud Function version within the affected ranges and has routing enabled with exposed HTTP endpoints that could trigger the recursive routing condition.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.16 / 4.1.10 / 4.2.6 or later
Fixed in 3.2.164.1.104.2.6
Interim mitigation

Upgrade Spring Cloud Function to version 3.2.16, 4.1.10, 4.2.6, 4.3.3, 5.0.2 or later to receive the patch that addresses the recursive routing vulnerability.

Recommended fix High confidence

Upgrade to 3.2.16+ (3.2.x), 4.1.10+ (4.1.x), 4.2.6+ (4.2.x), 4.3.3+ (4.3.x), or 5.0.2+ (5.0.x) depending on your current branch

  1. 1. Identify the current Spring Cloud Function version in your project by checking your dependency management (Maven pom.xml or Gradle build.gradle)
  2. 2. Determine which version branch you are currently on (3.2.x, 4.1.x, 4.2.x, 4.3.x, or 5.0.x)
  3. 3. For Spring Cloud Function 3.2.x: upgrade to version 3.2.16 or later
  4. 4. For Spring Cloud Function 4.1.x: upgrade to version 4.1.10 or later
  5. 5. For Spring Cloud Function 4.2.x: upgrade to version 4.2.6 or later
  6. 6. For Spring Cloud Function 4.3.x: upgrade to version 4.3.3 or later
  7. 7. For Spring Cloud Function 5.0.x: upgrade to version 5.0.2 or later
  8. 8. Update the version in your dependency management file (e.g., change spring-cloud-function.version property or direct dependency version)
Caveat Spring Cloud Function minor version upgrades typically maintain backward compatibility, but review release notes for any routing or configuration changes between your current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Cloud Function Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40989 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data