Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2026-40990

MEDIUM

Unbounded cache for function definitions

Also known asGHSA-x4h3-g2x4-8gqv
Published
Jun 1, 2026
Updated
Jul 15, 2026
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk11th percentile0.00%
0.00%0.24%0.47%0.71%0.2%0.2%Jul 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected
org.springframework.cloud:spring-cloud-function-contextorg.springframework.cloud:spring-cloud-function-contextorg.springframework.cloud:spring-cloud-function-contextorg.springframework.cloud:spring-cloud-function-contextorg.springframework.cloud:spring-cloud-function-context

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

5 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework.cloud:spring-cloud-function-context4.3.0&&< 4.3.34.3.3
Mavenorg.springframework.cloud:spring-cloud-function-context5.0.0&&< 5.0.25.0.2
Mavenorg.springframework.cloud:spring-cloud-function-context3.2.10No fix
Mavenorg.springframework.cloud:spring-cloud-function-context4.1.0No fix
Mavenorg.springframework.cloud:spring-cloud-function-context4.2.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-function-context. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.springframework.cloud:spring-cloud-function-context to 4.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40990 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-40990 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-40990. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-40990 in your dependencies?

O3 detects CVE-2026-40990 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.