CVE-2025-22232

MediumCVSS 5.3/10Last modified Jun 17, 2026

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.

Metrics

CVSS 3.1 5.3/10CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Weakness enumeration

Affected software

No affected versions have been published.

Timeline

Published
Apr 10, 2025
Last modified
Jun 17, 2026
NVD status
Deferred

Related CVEs from 2025

CVE-2025-222333.1CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter CVE-2025-222345.3The fix applied in CVE-2025-22228 inadvertently broke the timing attack mitigation implemented in DaoAuthenticationProvider. This can allow CVE-2025-222357.3EndpointRequest.to() creates a matcher for null/** if the actuator endpoint, for which the EndpointRequest has been created, is disabled or CVE-2025-222368.1Minion event bus authorization bypass. An attacker with access to a minion key can craft a message which may be able to execute a job on othCVE-2025-222376.7An attacker with access to a minion key can exploit the 'on demand' pillar functionality with a specially crafted git url which could cause CVE-2025-222384.2Directory traversal attack in minion file cache creation. The master's default cache is vulnerable to a directory traversal attack. Which coCVE-2025-222398.1Arbitrary event injection on Salt Master. The master's "_minion_event" method can be used by and authorized minion to send arbitrary events CVE-2025-22245.3The Directorist: AI-Powered Business Directory Plugin with Classified Ads Listings plugin for WordPress is vulnerable to unauthorized accessCVE-2025-222406.3Arbitrary directory creation or file deletion. In the find_file method of the GitFS class, a path is created using os.path.join using unvaliCVE-2025-222415.6File contents overwrite the VirtKey class is called when “on-demand pillar” data is requested and uses un-validated input to create paths toCVE-2025-222425.6Worker process denial of service through file read operation. .A vulnerability exists in the Master's “pub_ret” method which is exposed to aCVE-2025-222437.5VMware NSX Manager UI is vulnerable to a stored Cross-Site Scripting (XSS) attack due to improper input validation.
CVE-2025-22232: Medium severity, CVSS 5.3 | Vulnix