Spring Cloud FunctionFramework / library · VMware
CVE-2026-40990
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 · uneditedOOM 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.
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 confidenceThis is a Denial of Service vulnerability in Spring Cloud Function's Function Registry. The registry lacks proper input validation or limits on the number of functions that can be added, allowing an attacker to repeatedly add functions until memory is exhausted, causing an Out of Memory error.
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
>= 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.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Cloud Function dependencyReview your project's build configuration (pom.xml for Maven or build.gradle for Gradle) for the spring-cloud-function-core dependency and note its version.Affected if The version listed is one of the affected ranges: 3.2.0-3.2.15, 4.1.0-4.1.9, 4.2.0-4.2.5, 4.3.0-4.3.2, or 5.0.0-5.0.1.
-
Verify function registration endpoint exposureCheck your application configuration and network exposure settings to determine if the Spring Cloud Function registration endpoints (typically under /functionRouter or similar function registration paths) are accessible from untrusted network sources.Affected if The function registration endpoint is publicly or externally accessible without authentication.
-
Inspect function registry for unusual entriesAt runtime, inspect the Spring ApplicationContext function registry (via JMX, actuator /functions endpoint, or debugging) to count registered functions and look for any unexpected or suspiciously named functions.Affected if The registry contains an unexpectedly large number of functions or functions with names you did not deploy.
-
Review application logs for function registration activitySearch application logs for repeated 'FunctionRegistration' or similar registration messages that indicate automated or bulk function additions.Affected if Logs show a high frequency of function registration events in a short time period, especially from unexpected sources.
-
Check for rate limiting or input validationReview your Spring Cloud Function configuration for any custom RateLimiter implementations or input validation logic applied to the function registration mechanism.Affected if No custom rate limiting or bounds checking is configured on the function registration feature.
You are affected if your application runs a vulnerable version of Spring Cloud Function with an exposed function registration endpoint and you observe no rate limiting or validation on function registration activity.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.164.1.104.2.6
Upgrade Spring Cloud Function to version 3.2.16, 4.1.10, 4.2.6, 4.3.3, 5.0.2 or later, which contain bounds checking or limits on function registration.
Upgrade to Spring Cloud Function 3.2.16, 4.1.10, 4.2.6, 4.3.3, or 5.0.2 (whichever corresponds to your major version branch)
- Identify your project's build configuration file (pom.xml for Maven or build.gradle for Gradle)
- Locate the Spring Cloud Function dependency declaration
- Update the spring-cloud-function.version property or the direct dependency version to one of the fixed releases: 3.2.16, 4.1.10, 4.2.6, 4.3.3, or 5.0.2
- Run a dependency resolution to verify the upgrade succeeds (./mvnw dependency:tree or ./gradlew dependencies)
- Rebuild and test your application to ensure functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Cloud Function
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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