Skip to content
Fencer Vulns
high 8.6

CVE-2026-22739 json

Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks

published 2026-03-24 7 mo ago modified 2026-09-04 2 mo ago also GHSA-3qwq-q9vm-5j42 , EUVD-2026-14664

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known, plus a Nuclei check

Summary

Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud Config Server configured to the native file system as a backend, because it was possible to access files outside of the configured search directories.This issue affects Spring Cloud: from 3.1.X before 3.1.13, from 4.1.X before 4.1.9, from 4.2.X before 4.2.3, from 4.3.X before 4.3.2, from 5.0.X before 5.0.2.

Patch / fix

  • maven org.springframework.cloud:spring-cloud-config-server 4.3.2, 5.0.2
  • Spring Spring Cloud 3.1.13, 4.1.9, 4.2.3, 4.3.2, 5.0.2

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template Spring Cloud Config Server - Path Traversal nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.springframework.cloud:spring-cloud-config-server
>=4.3.0, <4.3.2
>=5.0.0-M1, <5.0.2
>=4.2.0, <=4.2.4
>=4.0.0, <=4.1.7
<=3.1.10
4.3.2
5.0.2

Affected products

  • Spring Spring Cloud

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.