CVE-2026-59436

Incorrectly Configured Access Control
Affects
Spring Cloud Config
in
Spring
No items found.
Versions
>=3.1.0 <=3.1.15, >=4.0.0 <=4.2.9, >=4.3.0 <=4.3.5, >=5.0.0 <=5.0.6

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server, applications get a central place to manage external properties across all environments, often served from Git repositories.

An incorrectly configured access control vulnerability (CVE-2026-59436) has been identified in the Spring Cloud Config Server, which allows attackers positioned on the network path to a Git server to impersonate that server, because SSH host key verification is silently turned off for a sub-repository whose host key configuration is incomplete. An attacker who can intercept the SSH connection can then serve the Config Server tampered configuration data.

Per OWASP: The Manipulator-in-the Middle attack (MITM) intercepts a communication between two systems.

This issue affects multiple versions of Spring Cloud Config.

Details

Module Info

Vulnerability Info

This Medium-severity vulnerability is found in the org.springframework.cloud:spring-cloud-config-server package in multiple versions of Spring Cloud Config.

The Config Server can use property-based SSH settings for a Git repository instead of the local ~/.ssh files by setting ignoreLocalSshSettings to true. This can be set on the top-level repository (spring.cloud.config.server.git.ignoreLocalSshSettings) or on any individual sub-repository under spring.cloud.config.server.git.repos. At startup, the HostKeyAlgoSupportedValidator and HostKeyAndAlgoBothExistValidator constraint validators are meant to reject an SSH repository whose host key settings are incomplete or unsupported, such as a hostKeyAlgorithm without a matching hostKey.

Both validators iterate over every extracted repository, but decide whether to validate each one by reading the flag from the top-level properties object rather than from the repository being checked:

for (JGitEnvironmentProperties extractedProperty : extractedProperties) {
    if (sshUriProperties.isIgnoreLocalSshSettings() && isSshUri(extractedProperty.getUri())) {
        validationResults.add(isAlgorithmSpecifiedWhenHostKeySet(extractedProperty, context)
                && isHostKeySpecifiedWhenAlgorithmSet(extractedProperty, context));
    }
}
return !validationResults.contains(false);

When the top-level repository keeps the default ignoreLocalSshSettings=false, the condition is false for every repository, so no host key checks run at all. A sub-repository that sets ignoreLocalSshSettings=true with an incomplete host key configuration therefore passes startup validation.

At runtime, PropertyBasedSshSessionFactory builds the SSH session for that sub-repository from its properties. Because no hostKey is set, it disables strict host key checking:

if (sshProperties.getHostKey() == null || !sshProperties.isStrictHostKeyChecking()) {
    hostEntry.setValue(SshConstants.STRICT_HOST_KEY_CHECKING, SshConstants.NO);
}

The Config Server then accepts any SSH server key when it fetches from that repository. An attacker who can intercept or redirect the SSH connection can present their own host key, impersonate the Git server, and supply arbitrary configuration that the Config Server distributes to its client applications. Exploitation requires that the Config Server uses a Git backend over SSH with a sub-repository configured this way.

Mitigation

Only recent versions of Spring Cloud Config receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.

Users of the affected components should apply one of the following mitigations:

  • Upgrade to a currently supported version of Spring Cloud Config.
  • Leverage a commercial support partner like HeroDevs for post-EOL security support.
Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Medium
ID
CVE-2026-59436
PROJECT Affected
Spring Cloud Config
Versions Affected
>=3.1.0 <=3.1.15, >=4.0.0 <=4.2.9, >=4.3.0 <=4.3.5, >=5.0.0 <=5.0.6
NES Versions Affected
Published date
November 19, 2026
≈ Fix date
Category
Incorrectly Configured Access Control
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Spring
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.