CVE-2026-59439

Denial of Service
Affects
Spring Cloud Function
in
Spring
No items found.
Versions
>=4.0.0 <=4.2.4, >=4.3.0 <=4.3.4, >=5.0.0 <=5.0.5

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

Spring Cloud Function is a Spring project that lets developers implement business logic as plain Java functions (Function, Supplier and Consumer beans) and run them unchanged across web endpoints, stream processors and serverless platforms, with the framework converting inbound messages to and from the function's input and output types.

A denial of service vulnerability (CVE-2026-59439) has been identified in the JSON message conversion of Spring Cloud Function, which allows attackers to exhaust application memory by sending a message whose payload is a very large JSON array. Because the framework places no limit on the number of elements it deserializes, the application can fail with OutOfMemory errors.

Per OWASP: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others. If a service receives a very large number of requests, it may cease to be available to legitimate users. In the same way, a service may stop if a programming vulnerability is exploited, or the way the service handles resources it uses.

This issue affects multiple versions of Spring Cloud Function.

Details

Module Info

Vulnerability Info

This Low-severity vulnerability is found in the org.springframework.cloud:spring-cloud-function-context package in multiple versions of Spring Cloud Function. It has a CVSS 3.1 base score of 3.1 (AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N).

When a function is invoked, Spring Cloud Function converts the inbound Message payload to the function's input type through its JsonMapper. When Jackson is on the classpath, ContextFunctionCatalogAutoConfiguration builds that mapper from the application's ObjectMapper (or a new one) and wraps it in a JacksonMapper, adjusting only a few serialization and deserialization features:

private JsonMapper jackson(ApplicationContext context) {
	Assert.state(ClassUtils.isPresent("com.fasterxml.jackson.databind.ObjectMapper", ClassUtils.getDefaultClassLoader()),
		"Can not bootstrap Jackson mapper since Jackson is not on the classpath");
	ObjectMapper mapper;
	try {
		mapper = context.getBean(ObjectMapper.class).copy();
	}
	catch (Exception e) {
		mapper = new ObjectMapper();
		mapper.registerModule(new JavaTimeModule());
	}
	mapper.registerModule(new JodaModule());
	// ...
	mapper.configure(SerializationFeature.FAIL_ON_EMPTY_BEANS, false);
	mapper.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false);
	return new JacksonMapper(mapper);
}

JacksonMapper then hands the raw payload straight to that mapper:

protected <T> T doFromJson(Object json, Type type) {
	T convertedValue = null;
	JavaType constructType = TypeFactory.defaultInstance().constructType(type);

	try {
		if (json instanceof String) {
			convertedValue = this.mapper.readValue((String) json, constructType);
		}
		else if (json instanceof byte[]) {
			convertedValue = this.mapper.readValue((byte[]) json, constructType);
		}
		// ...

No collection deserializer with a size bound is registered, so when the payload is a JSON array and the target type is a collection, Jackson's default deserializer reads every element and adds it to the resulting List or Set before the function runs. An attacker who can deliver a message to the function, for example through an HTTP endpoint or a message broker binding, can send an array with an arbitrarily large number of elements and force the application to materialize all of them in memory, leading to OutOfMemory errors (CWE-400, CWE-770) and making the application unavailable to legitimate users.

Mitigation

Only recent versions of Spring Cloud Function receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.

Users of the affected components should apply one of the following mitigations:

  • Upgrade to a currently supported version of Spring Cloud Function.
  • Leverage a commercial support partner like HeroDevs for post-EOL security support.

Credits

  • Yu Bao from PayPal Cyber Security Team (finder)
Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Low
ID
CVE-2026-59439
PROJECT Affected
Spring Cloud Function
Versions Affected
>=4.0.0 <=4.2.4, >=4.3.0 <=4.3.4, >=5.0.0 <=5.0.5
NES Versions Affected
Published date
November 20, 2026
≈ Fix date
Category
Denial of Service
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Spring
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.