CVE-2025-41235 json
CVE-2025-41235: Spring Cloud Gateway Server Forwards Headers from Untrusted Proxies
published last yr. modified last mo. also GHSA-6j2q-c73v-97c5 , EUVD-2025-16457
- cvss
- 8.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
Spring Cloud Gateway Server forwards the X-Forwarded-For and Forwarded headers from untrusted proxies.
Patch / fix
- maven org.springframework.cloud:spring-cloud-gateway-server 3.1.10, 4.1.8, 4.2.3
- maven org.springframework.cloud:spring-cloud-gateway-server-mvc 4.2.3
- VMware Spring cloud Gateway 4.3.0, 4.2.3, 4.1.8, 4.0.12, 3.1.10
- VMware Spring Cloud Gateway Server MVC 4.3.0, 4.2.3, 4.1.8
Is CVE-2025-41235 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
| GitHub | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.cloud:spring-cloud-gateway-server | >=4.2.0, <4.2.3 >=4.1.0, <4.1.8 >=4.0.0, <=4.0.9 <3.1.10 |
4.2.3 4.1.8 3.1.10 |
| maven | org.springframework.cloud:spring-cloud-gateway-server-mvc | >=4.1.7, <4.2.3 |
4.2.3 |
Affected products
- VMware Spring cloud Gateway
- VMware Spring Cloud Gateway Server MVC
Classification
- Weakness
-
- CWE-444 Inconsistent Interpretation of HTTP Requests
- Technology feeds
References
Sources
- CVE List CVE-2025-41235
- GitHub Advisory GHSA-6j2q-c73v-97c5
- NVD CVE-2025-41235
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.