CVE-2026-59437

Signature Forgery
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-side and client-side support for externalized configuration in a distributed system. Its Config Server gives applications a central place to manage external properties across all environments, and it commonly reads that configuration from a Git repository.

A signature forgery vulnerability (CVE-2026-59437) has been identified in the Spring Cloud Config Server, which allows attackers to impersonate the Git server with any SSH host key when property-based SSH settings are used without an explicit host key. An attacker who can intercept or redirect the connection can then serve modified configuration to the Config Server and the applications that rely on it.

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.

When a Git backend is configured with property-based SSH settings (spring.cloud.config.server.git.ignoreLocalSshSettings=true), the Config Server builds its SSH sessions through PropertyBasedSshSessionFactory. For each Git host, the factory decides whether to enforce strict host key checking:

JGitEnvironmentProperties sshProperties = sshKeysByHostname.get(hostName);

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

The getHostKey() == null branch turns strict host key checking off whenever no spring.cloud.config.server.git.hostKey is set, even though spring.cloud.config.server.git.strictHostKeyChecking is true by default. With StrictHostKeyChecking=no, the SSH client accepts whatever host key the remote end presents, and a host key list supplied through spring.cloud.config.server.git.knownHostsFile is never used to reject it. An attacker in a position to intercept the connection or spoof the Git server's address can complete the SSH handshake with their own key and serve arbitrary repository content, which the Config Server then hands out as configuration to its client applications.

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.

Until an upgrade is possible, set spring.cloud.config.server.git.hostKey, together with spring.cloud.config.server.git.hostKeyAlgorithm, for every Git repository that uses property-based SSH settings, so that the Git server's key is pinned explicitly.

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-59437
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 20, 2026
≈ Fix date
Category
Signature Forgery
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.