CVE-2025-22232
Spring Cloud Config Server May Not Use Vault Token Sent By Clients
- Published
- Updated
- Reserved
- Assigned by
- vmware
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| vmwareCNA (assigner) | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVDNVD · Deferred | 3.1 | Medium5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
- EPSS (exploitation in 30 days)
- 0.32% · top 75% of all CVEs (5 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.
Weakness
Affected products
- affected 4.2.x – < 4.2.2
- affected 4.1.x – < 4.1.6
- affected 4.0.x – < 4.0.10
- affected 3.1.x – < 3.1.10
- affected 3.0.x – < 4.1.6
- affected 2.2.x – < 4.1.6
What to do
Workaround: If you cannot upgrade, then you can either: * Remove Spring Vault from the classpath if it is not needed or * Implement your own SessionManager that does not persist the Vault token and provide a bean using that implementation in a @Configuration class. For example: public class StatelessSessionManager implements SessionManager { private final ClientAuthentication clientAuthentication; private final ReentrantLock lock = new ReentrantLock(); public StatelessSessionManager(ClientAuthentication clientAuthentication) { Assert.notNull(clientAuthentication, "ClientAuthentication must not be null"); this.clientAuthentication = clientAuthentication; } public VaultToken getSessionToken() { this.lock.lock(); try { return this.clientAuthentication.login(); } finally { this.lock.unlock(); } } } @Configuration public class MySessionManagerConfiguration extends SpringVaultClientConfiguration { private final VaultEnvironmentProperties vaultProperties; public MySessionManagerConfiguration(VaultEnvironmentProperties vaultProperties, ConfigTokenProvider configTokenProvider, List<springvaultclientauthenticationprovider> authProviders) { super(vaultProperties, configTokenProvider, authProviders); this.vaultProperties = vaultProperties; } @Bean @Primary public SessionManager sessionManager() { if (vaultProperties.getAuthentication() == null && !StringUtils.hasText(vaultProperties.getToken())) { return new StatelessSessionManager(clientAuthentication()); } return super.sessionManager(); } } </springvaultclientauthenticationprovider>
References (1)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2025-22232)Record last updated .