CVE-2026-59297

Spring Cloud Function can incorrectly determine if URI is secure

Published Aug 27, 2026 CVSS 3.1 · 3.1 Low EPSS < 1% KEV · Not listed
Description
Implementation of isSecure() call of ServerlessHttpServletRequest does not verify the actual scheme.
Spring Cloud Function 5.0.0 - 5.0.3
Spring Cloud Function 4.3.0 - 4.3.4
Spring Cloud Function 4.2.0 - 4.2.7

Analysis

AI-generated

Technical impact

The flaw lies in ServerlessHttpServletRequest’s isSecure() implementation, which fails to verify the actual URI scheme. As a result, an HTTP request can be reported as secure, allowing an application that relies on isSecure() to treat an insecure connection as if it were encrypted. This misidentification does not enable direct code execution or data theft, but it undermines security controls that depend on accurate scheme verification and can lead to authentication bypass or unauthorized data exposure. The weakness is classified as CWE-346 (Insecure Direct Object Reference). The CVE description does not provide a specific attack vector, but it is inferred that an attacker could trigger the misreport by sending a request that meets the application’s criteria for a secure connection while remaining unencrypted.

Affected Systems

Spring Cloud Function versions 5.0.0 through 5.0.3, 4.3.0 through 4.3.4, and 4.2.0 through 4.2.7 are vulnerable.

Risk and Exploitability

The CVSS score of 3.1 indicates low severity, and the EPSS score of less than 1% reflects a very low likelihood of exploitation at this time. The vulnerability is not listed in the CISA KEV catalog. Because the issue merely misreports the scheme, it does not provide a direct remote code execution vector; however, if an environment depends on isSecure() to enforce encryption or authentication, the flaw could be leveraged to bypass those controls and expose data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor-provided patch for Spring Cloud Function when it becomes available.
  • Ensure that all serverless functions are accessed only through HTTPS endpoints, and terminate TLS before reaching the function runtime.
  • Replace any logic that depends on isSecure() with explicit scheme checks or additional security controls to verify that the connection is truly encrypted.

Generated by OpenCVE AI on August 29, 2026 at 00:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Cloud Function
CPEs cpe:2.3:a:vmware:spring_cloud_function:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Cloud Function
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
Weaknesses CWE-346
Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
First Time appeared Spring
Spring spring Cloud Function
Vendors & Products Spring
Spring spring Cloud Function
Type Values Removed Values Added
Description Implementation of isSecure() call of ServerlessHttpServletRequest does not verify the actual scheme. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7
Title Spring Cloud Function can incorrectly determine if URI is secure
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 6:35 PM
Reserved
Jul 4, 2026, 6:13 PM
Status
Analyzed
Published
Aug 27, 2026, 8:17 PM
Modified
Sep 2, 2026, 5:27 PM