CVE-2026-40989
Self Routing guard bypassed via function composition
No known exploitation. EPSS puts it in the 11th percentile. Fixed versions are out.
No public exploit knownFix2 products4 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.180049
What to do
Find your product and version, then upgrade to the build on the right.
- Spring Cloud FunctionAffected: ≥ 3.2.0, < 3.2.16Upgrade to: 3.2.16Affected: ≥ 4.1.0, < 4.1.10Upgrade to: 4.1.10Affected: ≥ 4.2.0, < 4.2.6Upgrade to: 4.2.6Affected: ≥ 4.3.0, < 4.3.3Upgrade to: 4.3.3 + 1 more branchStated by: CVE record
- Vmware Spring Cloud FunctionAffected: ≥ 3.2.0, < 3.2.16Upgrade to: 3.2.16Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 11th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
8 events over 51 days, from the signal feeds we watch.
- Patch availablerecord updated
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:H
Scored 5.7 by NVD.
How it is reached
- Attack Vector PhysicalRequires physical access to the device
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity LowData modification is possible but limited in scope or consequence
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Spring Cloud Function, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI