CVE-2026-59297 json
Spring Cloud Function can incorrectly determine if URI is secure
published 2026-08-27 2 mo ago modified 2026-09-02 2 mo ago also EUVD-2026-67183
- cvss
- 3.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
Implementation of isSecure() call of ServerlessHttpServletRequest does not verify the actual scheme. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7
Patch / fix
- vmware spring_cloud_function 4.2.8, 4.3.5, 5.0.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N |
Affected products
- Spring Spring Cloud Function
Classification
- Weakness
-
- CWE-346 Origin Validation Error
- Technology feeds
References
-
spring.io
/security/cve-2026-59297
vendor-advisory
Sources
- CVE List CVE-2026-59297
- NVD CVE-2026-59297
Fencer Vulns 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.