CVE-2026-59284 json
Spring Cloud Commons no allow list for writable env actuator endpoint
published 2026-08-27 2 mo ago modified 2026-09-01 2 mo ago also EUVD-2026-67173
- cvss
- 7.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 37%
- public exploits
- 0
- none known
Summary
There is no allow list for property keys when Spring Cloud Commons writable /actuator/env is enabled. Spring Cloud Commons 5.0.0 - 5.0.2 Spring Cloud Commons 4.3.0 - 4.3.3 Spring Cloud Commons 4.0.0 - 4.2.6 Spring Cloud Commons 3.1.10 and earlier
Patch / fix
- broadcom spring_cloud_commons 3.1.11, 4.2.7, 4.3.4, 5.0.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-59284 updated cvss 7.6
org.springframework.cloud/spring-cloud-commons: Spring Cloud Commons: Integrity compromise via writable /actuator/env endpoint
-
Red Hat Fuse 7 spring-cloud-commons 3.0.5not affected: vulnerable code not in execute path
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:L |
Affected products
- Spring Spring Cloud Commons
Classification
- Weakness
-
- CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
- Technology feeds
References
-
spring.io
/security/cve-2026-59284
vendor-advisory
Sources
- CVE List CVE-2026-59284
- NVD CVE-2026-59284
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.