CVE-2025-22232 Details
Description
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.
A vulnerability exists in Spring Cloud Config Server versions 2.2.1.RELEASE through 4.2.1, where the server may not properly utilize Vault tokens sent by clients via the X-CONFIG-TOKEN header when making requests to Vault. This issue arises if Spring Vault is included in the classpath of the Config Server, the X-CONFIG-TOKEN header is used to transmit a Vault token, and the default SessionManager implementation, LifecycleAwareSessionManager, or a similar implementation that retains the Vault token, such as SimpleSessionManager, is in use. The SessionManager will save the first token it receives and continue to use it, disregarding any subsequent tokens provided in client requests.
Users of affected versions should upgrade to Spring Cloud Config 4.2.2, 4.1.6, or 4.0.10, depending on their current version. Note that Spring Cloud Config 3.0.x and 2.2.x are no longer supported, and users should upgrade to a supported version. If an upgrade is not possible, remove Spring Vault from the classpath if it is not needed, or implement a custom SessionManager that does not persist the Vault token and provide a bean with that implementation in a @Configuration class.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Apr 10, 2025CISA-ADP
Assessed Apr 10, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://spring.io/security/cve-2025-22232 | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-287 | Improper Authentication | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| VMware Spring Cloud Config | >= 2.2.1.RELEASE, <= 4.2.1 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 10, 2025 | New CVE Received | [email protected] |
Volerion