CVE-2026-59291 json
Potential arbitrary file read and SSRF vulnerability in Spring Cloud Function
published 2mo ago modified 2mo ago also EUVD-2026-67179
- cvss
- 2.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Potential arbitrary file read and SSRF vulnerability in Spring Cloud Function. 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
Is CVE-2026-59291 in your stack? 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
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.0 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N |
Affected products
- Spring Spring Cloud Function
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
-
spring.io
/security/cve-2026-59291
vendor-advisory
Sources
- CVE List CVE-2026-59291
- NVD CVE-2026-59291
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.