Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Spring Cloud Function Context: Uncontrolled Recursion is possible while attempting to add infinite amount of functions to Function RegistryGHSA-x4h3-g2x4-8gqv

MEDIUM

GHSA-x4h3-g2x4-8gqv is a medium-severity (CVSS 5.7) CWE-770 vulnerability in org.springframework.cloud:spring-cloud-function-context. A fix is available for org.springframework.cloud:spring-cloud-function-context — see the affected versions and patch details below.

Also known asCVE-2026-40990
Published
Updated
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed
Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-x4h3-g2x4-8gqv.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk
0.00%0.26%0.52%0.78%0.2%0.2%0.2%0.3%0.3%Jul 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-x4h3-g2x4-8gqv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 389,824 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

5 pkgs affected
☕org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-context☕org.springframework.cloud:spring-cloud-function-context☕org.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-context≥ 4.3.0&&< 4.3.34.3.3org.springframework.cloud:spring-cloud-function-context:4.3.3
☕Mavenorg.springframework.cloud:spring-cloud-function-context≥ 5.0.0&&< 5.0.25.0.2org.springframework.cloud:spring-cloud-function-context:5.0.2
☕Mavenorg.springframework.cloud:spring-cloud-function-context≥ 3.2.10No fix
☕Mavenorg.springframework.cloud:spring-cloud-function-context≥ 4.1.0No fix
☕Mavenorg.springframework.cloud:spring-cloud-function-context≥ 4.2.0No fix

Affected Products

1 product · 5 configurations
Application
spring cloud functionvmware
≥ 5.0.0 && < 5.0.2
range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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 GHSA-x4h3-g2x4-8gqv is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat's versions of spring-cloud-function shipped as a transitive dependency in EAP XP predate the affected version range and are not impacted by this vulnerability.

Workaround published by Red Hat
No mitigation is required. The shipped versions do not contain the vulnerable code.
Source: Red Hat security advisory for GHSA-x4h3-g2x4-8gqv (CC BY 4.0)

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 GHSA-x4h3-g2x4-8gqv in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Spring Cloud Function Context: Uncontrolled Recursion is…