MediumGHSA-j6hh-h3cf-c2hfCVE-2026-41004

Spring Cloud Config Server Logged Sensitive Information

Published 7 May 2026 · Updated 18 Jun 2026

Is your project on an affected org.springframework.cloud:spring-cloud-config-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=3.1.0 <=3.1.13
Fixed in
No fix released
Affected
>=4.1.0 <=4.1.9
Fixed in
No fix released
Affected
>=4.2.0 <=4.2.6
Fixed in
No fix released
Affected
>=4.3.0 <4.3.3
Fixed in
4.3.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.cloud:spring-cloud-config-server -DdepVersion=4.3.3 -DforceVersion=true
Affected
>=5.0.0 <5.0.3
Fixed in
5.0.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.springframework.cloud:spring-cloud-config-server -DdepVersion=5.0.3 -DforceVersion=true
Affected
>=3.0.0 <=3.0.7
Fixed in
No fix released

Details

When trace logging is enabled in Spring Cloud Config Server, sensitive information is placed in plain text in the logs.

  • Spring Cloud Config 3.0.x: affected from 3.0.0 through 3.0.7 (inclusive); no open-source upgrade available.
  • Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); no open-source upgrade available.
  • Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); no open-source upgrade available.
  • Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); no open-source upgrade available.
  • Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater.
  • Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.

Is GHSA-j6hh-h3cf-c2hf in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework.cloud:spring-cloud-config-server, and gives you the command that fixes it.

More advisories for org.springframework.cloud:spring-cloud-config-server

  • CriticalCVE-2026-40982Spring Cloud Config vulnerable to Path Traversal · 7 May 2026
  • HighCVE-2026-40981Spring Cloud Config has an Authorization Bypass Through User-Controlled Key · 7 May 2026
  • HighCVE-2026-41002Spring Cloud Config Server Susceptible To TOCTOU Attack · 7 May 2026
  • HighCVE-2026-22739Spring Cloud Config Server: Path Traversal via Profile Parameter Allows Arbitrary File Access · 24 Mar 2026
  • HighCVE-2020-5410Directory traversal attack in Spring Cloud Config · 5 Jun 2020
  • MediumCVE-2020-5405Directory traversal attack in Spring Cloud Config · 5 Jun 2020
All 8 advisories for org.springframework.cloud:spring-cloud-config-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.