Skip to content
Fencer Intel
critical 10.0

CVE-2025-41243 json

Spring Expression Language property modification using Spring Cloud Gateway Server WebFlux

published last yr. modified 22d ago also GHSA-q2cj-h8fw-q4cc , EUVD-2025-29611

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known, plus a Nuclei check

Summary

Spring Cloud Gateway Server Webflux may be vulnerable to Spring Environment property modification.

An application should be considered vulnerable when all the following are true:

* The application is using Spring Cloud Gateway Server Webflux (Spring Cloud Gateway Server WebMVC is not vulnerable). * Spring Boot actuator is a dependency. * The Spring Cloud Gateway Server Webflux actuator web endpoint is enabled via management.endpoints.web.exposure.include=gateway. * The actuator endpoints are available to attackers. * The actuator endpoints are unsecured.

Patch / fix

  • maven org.springframework.cloud:spring-cloud-gateway-server-webflux 4.2.5, 4.3.1
  • Spring Cloud Gateway 3.1.11, 4.1.11, 4.2.5, 4.3.1

Is CVE-2025-41243 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

3.67% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Spring Cloud Gateway Server Webflux - Broken Access Control nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.cloud:spring-cloud-gateway-server-webflux
>=3.1.0, <=3.1.10
>=4.0.0, <=4.1.10
>=4.2.0, <4.2.5
>=4.3.0, <4.3.1
4.2.5
4.3.1

Affected products

  • Spring Cloud Gateway

Classification

Weakness
  • CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.