Is org.springframework.cloud:spring-cloud-config-server 4.3 vulnerable?
Maven · 5 releases from 4.3.0 to 4.3.4 · latest org.springframework.cloud:spring-cloud-config-server is 5.0.6 · checked 18 Nov 2026
No known advisories in the last release
org.springframework.cloud:spring-cloud-config-server 4.3.4, the last 4.3 release, has no known advisories. 5 advisories affect earlier 4.3.x releases, so update to 4.3.4.
mvn versions:use-dep-version -Dincludes=org.springframework.cloud:spring-cloud-config-server -DdepVersion=4.3.4 -DforceVersion=trueIs your project on an affected org.springframework.cloud:spring-cloud-config-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.3.x, affecting earlier releases
Spring Cloud Config vulnerable to Path Traversal
- Affected
- <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config has an Authorization Bypass Through User-Controlled Key
- Affected
- >=3.1.0 <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config Server Susceptible To TOCTOU Attack
- Affected
- >=3.1.0 <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3 · >=3.0.0 <=3.0.7
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config Server Logged Sensitive Information
- Affected
- >=3.1.0 <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3 · >=3.0.0 <=3.0.7
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config Server: Path Traversal via Profile Parameter Allows Arbitrary File Access
- Affected
- >=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
- Fixed in
- 4.3.2, 5.0.2
Every org.springframework.cloud:spring-cloud-config-server 4.3.x release
Affected: 4.3.0 to 4.3.2. 4.3.3 and later are not affected. Latest org.springframework.cloud:spring-cloud-config-server: 5.0.6.
| Version | Known advisories |
|---|---|
| org.springframework.cloud:spring-cloud-config-server 4.3.4 | None |
| org.springframework.cloud:spring-cloud-config-server 4.3.3 | None |
| org.springframework.cloud:spring-cloud-config-server 4.3.2 | CVE-2026-40982, CVE-2026-40981, CVE-2026-41002, CVE-2026-41004 |
| org.springframework.cloud:spring-cloud-config-server 4.3.1 | CVE-2026-40982, CVE-2026-40981, CVE-2026-41002, CVE-2026-41004, CVE-2026-22739 |
| org.springframework.cloud:spring-cloud-config-server 4.3.0 | CVE-2026-40982, CVE-2026-40981, CVE-2026-41002, CVE-2026-41004, CVE-2026-22739 |
Which of your client projects are still on org.springframework.cloud:spring-cloud-config-server 4.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.springframework.cloud:spring-cloud-config-server version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.springframework.cloud:spring-cloud-config-server versions
- org.springframework.cloud:spring-cloud-config-server 5.0
- org.springframework.cloud:spring-cloud-config-server 4.2
- org.springframework.cloud:spring-cloud-config-server 4.1
- org.springframework.cloud:spring-cloud-config-server 4.0
- org.springframework.cloud:spring-cloud-config-server 3.1
- org.springframework.cloud:spring-cloud-config-server 3.0
- All org.springframework.cloud:spring-cloud-config-server advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.