CVE-2026-41850
Description
Spring Framework vulnerable to Algorithmic Denial of Service via user-supplied SpEL expressions, impacting availability.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Spring Framework vulnerable to Algorithmic Denial of Service via user-supplied SpEL expressions, impacting availability.
Vulnerability
Applications that evaluate user-supplied Spring Expression Language (SpEL) expressions are vulnerable to an Algorithmic Denial of Service (DoS). An application is vulnerable when it accepts and evaluates untrusted or user-controlled SpEL expressions. Affected versions include Spring Framework 7.0.0 through 7.0.7, 6.2.0 through 6.2.18, 6.1.0 through 6.1.27, and 5.3.0 through 5.3.48 [1].
Exploitation
An attacker can exploit this vulnerability by providing a specially crafted SpEL expression. This expression triggers excessive resource consumption during the evaluation process, leading to application degradation or unavailability. No specific network position, authentication, or user interaction is mentioned as a prerequisite in the available references [1].
Impact
Successful exploitation of this vulnerability can lead to an Algorithmic Denial of Service (DoS) condition. This results in excessive resource consumption, causing application degradation or complete unavailability. The impact is on the availability of the application [1].
Mitigation
Users of affected versions should upgrade to the corresponding fixed versions: Spring Framework 7.0.8, 6.2.19, 6.1.28, or 5.3.49. Versions that are no longer supported are also affected. No further mitigation steps are necessary beyond upgrading [1].
AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: 7.0.0-7.0.7, 6.2.0-6.2.18, 6.1.0-6.1.27, 5.3.0-5.3.48
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Spring Framework: 13 Vulnerabilities Disclosed on June 9, 2026Vypr Intelligence · Jun 9, 2026