CVE-2025-22232 Spring Cloud Config Server May Not Use Vault Token Sent By Clients
Spring Cloud Config Server may ignore client-provided Vault tokens, causing it to reuse a persisted token and bypass intended authentication controls.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-22232?
CVE-2025-22232 is a medium-severity authentication bypass vulnerability in Spring Cloud Config, published on 10 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2025-22232?
How do I fix CVE-2025-22232?
No fix has been published for CVE-2025-22232 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-22232 being exploited?
There is no known exploitation of CVE-2025-22232 in the wild and no public exploit code.
Sources
Also known as GHSA-qpfh-2wpm-c362.