dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-41243

CRITICAL · 10.0 CVSS v3.1 Published 2025-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring Cloud Gateway Server Webflux with the actuator gateway endpoint enabled and exposed without authentication allows attackers to modify Spring Environment properties, potentially leading to remote code execution or complete system compromise. The vulnerability requires the specific combination of Webflux (not WebMVC), actuator dependency, exposed gateway endpoint, and unsecured access.

MitigationSecure or disable the actuator gateway endpoint by either adding authentication/authorization to actuator endpoints or removing the gateway actuator from management.endpoints.web.exposure.include, and restrict network access to actuator endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Spring Cloud Gateway with Webflux is in use
    Inspect project dependencies (pom.xml, build.gradle) for spring-cloud-starter-gateway and verify spring-boot-starter-webflux is present while spring-boot-starter-web is absent. Check if the application class extends ReactiveWebApplicationContext or uses Reactive patterns.
    Affected if The application uses Spring Cloud Gateway with Webflux (Reactive) rather than Spring WebMVC.
  2. Verify actuator dependency is included
    Inspect project build files for spring-boot-starter-actuator or spring-cloud-starter-gateway-actuator dependency.
    Affected if The actuator dependency is present in the project.
  3. Check if gateway actuator endpoint is exposed
    Inspect application.yml/properties for management.endpoints.web.exposure.include configuration. Look for 'gateway' in the exposed endpoints list (e.g., management.endpoints.web.exposure.include=health,info,gateway).
    Affected if The 'gateway' endpoint is listed in management.endpoints.web.exposure.include.
  4. Verify actuator endpoints lack authentication
    Inspect Spring Security configuration (SecurityFilterChain bean) and management.server.port/management.endpoints.web.base-path settings. Confirm no security constraints are applied to /actuator/gateway/** paths and no authentication is required.
    Affected if Actuator gateway endpoint is accessible without authentication (no Spring Security config securing /actuator paths, or management server not restricting access).
  5. Check network accessibility of actuator endpoints
    Review firewall rules, network policies, or reverse proxy configuration. Test if the actuator endpoints are reachable from untrusted networks (e.g., curl http://<host>:<port>/actuator/gateway).
    Affected if The /actuator/gateway endpoint is reachable from network locations that should not have access.

A user is affected if their Spring Cloud Gateway uses Webflux, has the actuator dependency with the gateway endpoint explicitly exposed, and lacks authentication/authorization protecting the /actuator/gateway/** endpoints from unauthorized network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Secure or disable the actuator gateway endpoint by either adding authentication/authorization to actuator endpoints or removing the gateway actuator from management.endpoints.web.exposure.include, and restrict network access to actuator endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41243 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data