CVE-2025-22232
Spring Cloud Config Server May Not Use Vault Token Sent By Clients
Reported by vmware · Published April 10, 2025
Spring Cloud Config Server may not use Vault token sent by clients using a X-CONFIG-TOKEN header when making requests to Vault. Your application may be affected by this if the following are true: * You have Spring Vault on the classpath of your Spring Cloud Config Server and * You are using the X-CONFIG-TOKEN header to send a Vault token to the Spring Cloud Config Server for the Config Server to use when making requests to Vault and * You are using the default Spring Vault SessionManager implementation LifecycleAwareSessionManager or a SessionManager implementation that persists the Vault token such as SimpleSessionManager. In this case the SessionManager persists the first token it retrieves and will continue to use that token even if client requests to the Spring Cloud Config Server include a X-CONFIG-TOKEN header with a different value. Affected Spring Products and Versions Spring Cloud Config: * 2.2.1.RELEASE - 4.2.1 Mitigation Users of affected versions should upgrade to the corresponding fixed version. Affected version(s)Fix versionAvailability4.2.x4.2.2OSS4.1.x4.1.6OSS4.0.x4.0.10Commercial3.1.x3.1.10Commercial3.0.x4.1.6OSS2.2.x4.1.6OSS NOTE: Spring Cloud Config 3.0.x and 2.2.x are no longer under open source or commercial support. Users of these versions are encouraged to upgrade to a supported version. No other mitigation steps are necessary.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Spring Cloud Config | Spring | 4.2.2, 4.1.6, 4.0.10, 3.1.10 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Spring | Spring Cloud Config | 4.2.x, 4.1.x, 4.0.x |
| Spring | Spring Cloud Config | 4.2.x, 4.1.x, 4.0.x |
Timeline
- Apr 8, 2025 CVE Published
- Apr 10, 2025 PoC Published (2 in total, the first dated here)
- Apr 11, 2025 EPSS Score (30 in total, the first dated here)
- Jun 9, 2025 Coalition ESS Score (9 in total, the first dated here)
- Dec 21, 2025 CVE Updated
- Apr 1, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-22232
vulnetix vdb fixes CVE-2025-22232
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-22232/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart