CVE-2025-22232Network attack vector

Cross-client Vault disclosure via persisted first token

Published Apr 10, 2025 · Updated Apr 10, 2025

Improper authentication in Spring Cloud Config 2.2.1.RELEASE through 4.2.1 allows remote attackers to receive another client's Vault data. The configured SessionManager caches the first X-CONFIG-TOKEN value and reuses it instead of honoring a different token on a later request. Exposure requires Spring Vault, client-supplied token headers, and a token-persisting SessionManager; the result is cross-client disclosure of Vault-backed configuration.

CVSS severity5.3
Medium
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in Spring Cloud Config 2.2.1.RELEASE through 4.2.1 allows remote attackers to receive another client's Vault data. The configured SessionManager caches the first X-CONFIG-TOKEN value and reuses it instead of honoring a different token on a later request. Exposure requires Spring Vault, client-supplied token headers, and a token-persisting SessionManager; the result is cross-client disclosure of Vault-backed configuration.

The record

CVE
CVE-2025-22232
Published
Apr 10, 2025
Updated
Apr 10, 2025
Vendor
Spring
Product
Spring Cloud Config
Classifications
CWE-287, T1555
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 10, 2025CVE publishedPublication date reported by the CVE source.
  2. Apr 10, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.2.x <4.1.6
  2. Affected versionversion=3.0.x <4.1.6
  3. Affected versionversion=3.1.x <3.1.10
  4. Affected versionversion=4.0.x <4.0.10
  5. Affected versionversion=4.1.x <4.1.6
  6. Affected versionversion=4.2.x <4.2.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Spring · Spring Cloud Configversion=2.2.x <4.1.6; version=3.0.x <4.1.6; version=3.1.x <3.1.10; version=4.0.x <4.0.10; version=4.1.x <4.1.6; version=4.2.x <4.2.2

Published CVSS scores

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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-287Improper Authentication
T1555Credentials from Password Stores

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo