What is CVE-2025-41243?

CVE-2025-41243 is a critical-severity code injection vulnerability in org.springframework.cloud:spring-cloud-gateway-server-webflux (maven), affecting versions >= 3.1.0, <= 3.1.10. It is fixed in 4.2.5, 4.3.1. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2025-41243?

CVE-2025-41243 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Is there a fix for CVE-2025-41243?

Yes. CVE-2025-41243 is fixed in 4.2.5, 4.3.1. Upgrade to this version or later.

Is CVE-2025-41243 exploitable, and should I be worried?

Whether CVE-2025-41243 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-41243 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-41243 in org.springframework.cloud:spring-cloud-gateway-server-webflux | Intelligent Application Security

Q: How severe is CVE-2025-41243?

CVE-2025-41243 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2025-41243?

Yes. CVE-2025-41243 is fixed in 4.2.5, 4.3.1. Upgrade to this version or later.

Q: Is CVE-2025-41243 exploitable, and should I be worried?

Whether CVE-2025-41243 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-41243 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-41243?

Upgrade: org.springframework.cloud:spring-cloud-gateway-server-webflux to 4.2.5 or later, org.springframework.cloud:spring-cloud-gateway-server-webflux to 4.3.1 or later.

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.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2025-41243 has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.2.5, 4.3.1); upgrading removes the vulnerable code path.

Affected versions

org.springframework.cloud:spring-cloud-gateway-server-webflux (>= 3.1.0, <= 3.1.10) org.springframework.cloud:spring-cloud-gateway-server-webflux (>= 4.0.0, <= 4.1.10) org.springframework.cloud:spring-cloud-gateway-server-webflux (>= 4.2.0, < 4.2.5) org.springframework.cloud:spring-cloud-gateway-server-webflux (>= 4.3.0, < 4.3.1)

Security releases

org.springframework.cloud:spring-cloud-gateway-server-webflux → 4.2.5 (maven) org.springframework.cloud:spring-cloud-gateway-server-webflux → 4.3.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.springframework.cloud:spring-cloud-gateway-server-webflux to 4.2.5 or later; org.springframework.cloud:spring-cloud-gateway-server-webflux to 4.3.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-41243? CVE-2025-41243 is a critical-severity code injection vulnerability in org.springframework.cloud:spring-cloud-gateway-server-webflux (maven), affecting versions >= 3.1.0, <= 3.1.10. It is fixed in 4.2.5, 4.3.1. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2025-41243? CVE-2025-41243 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.springframework.cloud:spring-cloud-gateway-server-webflux are affected by CVE-2025-41243? org.springframework.cloud:spring-cloud-gateway-server-webflux (maven) versions >= 3.1.0, <= 3.1.10 is affected.
Is there a fix for CVE-2025-41243? Yes. CVE-2025-41243 is fixed in 4.2.5, 4.3.1. Upgrade to this version or later.
Is CVE-2025-41243 exploitable, and should I be worried? Whether CVE-2025-41243 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-41243 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-41243?
- Upgrade org.springframework.cloud:spring-cloud-gateway-server-webflux to 4.2.5 or later
- Upgrade org.springframework.cloud:spring-cloud-gateway-server-webflux to 4.3.1 or later