S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Oct 28, 2025

CVE-2025-41243 Scanner

CVE-2025-41243 Scanner - Broken Access Control vulnerability in Spring Cloud Gateway Server Webflux

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3.2k
Times Used
continuous scan runs
4.7k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-41243
10.0
CVSScritical
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
Cloud Gatewayby Spring
AFFECTED< 4.3.1SAFE ✓≥ 4.3.1
Updated Aug 22, 2026View on NVD →
Detail

Spring Cloud Gateway Server Webflux is widely used by organizations to route and manage service requests in microservices architectures. It facilitates API monitoring, discovery, and management operations, offering capabilities to handle cross-origin requests, rate limiting, and more. The software is commonly deployed by enterprises seeking to enhance the scalability and reliability of their cloud-based applications. Microservices developers and system administrators leverage this platform to deliver seamless and efficient service communication. It integrates smoothly with other Spring components to provide a comprehensive framework for cloud-based applications. Its actuator endpoints are used for monitoring and managing Spring Boot application systems but can be exposed if these endpoints are unsecured.

The vulnerability pertains to unsecured actuator endpoints, which can be exploited for unauthorized access and configuration modifications. This security flaw allows attackers to alter Spring Environment properties through a method of code injection. With this, attackers can manipulate application behavior dynamically, potentially leading to service disruption or sensitive data exposure. This vulnerability underscores the critical need for securing administrative interfaces and considering the implementation of robust access controls. Exploiting this weakness usually requires no authentication, hence escalating its criticality. This code injection flaw could also pave the way for further systemic attacks once accessed.

At a technical level, the vulnerability arises from unsecured exposure of actuator endpoints that allow manipulation via HTTP requests. Attackers can utilize crafted HTTP POST requests to actuator endpoints like `/actuator/gateway/routes` and `/actuator/gateway/refresh` for injecting unsafe code. These endpoints should relay information but their exposure without security enables setting dynamic properties which modify how the gateway behaves in runtime. The specific method of injection involves exploiting the behavior of the JSON payload in HTTP requests to alter response headers or environment settings vulnerably. Moreover, this exploitation method requires precise interactions with said endpoints under unsecured conditions to fulfill the attack vector.

If successfully exploited, this vulnerability could result in unauthorized configuration changes leading to altered behavior of various services within an organization's network. Attackers could potentially disable critical security properties or implement malicious configurations unnoticed. This might result in further unauthorized access, data leaks, and the integrity of the system being compromised. Organizations might face disruption in their services, reputation damage, and possible legal penalties. Additionally, alterations to properties can further allow for other vulnerabilities to be exploited more effectively.

REFERENCES

Solution Advice
  • Secure actuator endpoints by implementing strict access controls or completely disabling unnecessary endpoints.
  • Regularly update Spring Cloud Gateway Server Webflux to the latest version to include patches for known vulnerabilities.
  • Use network firewalls and security tools to limit access to your microservices' management endpoints.
  • Review and secure your deployment configurations to ensure no sensitive information is exposed through actuator endpoints.
  • Conduct regular security audits and penetration testing on your microservices infrastructure.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.