# CVE-2026-59301: Spring Cloud Function Azure sensitive data logging

Source: https://junglewise.ai/threats/cve-2026-59301-spring-cloud-function-azure-sensitive-data-logging  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-27. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-59301 · Severity: low · CVSS 3.1 · Published 2026-08-27

Spring Cloud Function is a framework used to build serverless functions that integrate with cloud platforms like Azure. A flaw in versions 4.2.0–4.2.7, 4.3.0–4.3.4, and 5.0.0–5.0.3 can cause sensitive data (such as credentials or API keys) to be written to application logs, potentially exposing it to unauthorized users with log access.

Technologies: [VMware Spring Cloud Function](https://junglewise.ai/threats/technologies/spring-cloud-function). Vendors: [VMware](https://junglewise.ai/threats/vendors/vmware).

## Quick answers

**Is CVE-2026-59301 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59301 being exploited in the wild.

**How severe is CVE-2026-59301?** Low severity, with a CVSS score of 3.1, published 27 August 2026.

**Which products and versions are affected?** VMware Spring Cloud Function 4.2.0 - 4.2.7, 4.3.0 - 4.3.4, 5.0.0 - 5.0.3.

**Is there a fix for CVE-2026-59301?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-59301 attacked?** It is attacked from the adjacent network, in a software library.

**Am I affected by CVE-2026-59301?** Check whether you run VMware Spring Cloud Function at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an information disclosure issue in Spring Cloud Function's Azure integration where sensitive data may be logged without proper redaction. The root cause involves insufficient sanitization of function parameters or configuration values before they are written to log output. An attacker with access to application logs (via cloud provider dashboards, centralized logging systems, or file access) can retrieve credentials or other sensitive configuration. No special network access or authentication bypass is required beyond existing log visibility. Patches are available in versions 4.2.8+, 4.3.5+, and 5.0.4+.

## Affected products

- VMware Spring Cloud Function 4.2.0 - 4.2.7, 4.3.0 - 4.3.4, 5.0.0 - 5.0.3

## Timeline

- 2026-08-27: disclosed

## References

- [https://spring.io/security/cve-2026-59301](https://spring.io/security/cve-2026-59301)

## Related threats

- [Spring Cloud Function sensitive data logging in AWS integration](https://junglewise.ai/threats/cve-2026-59300-spring-cloud-function-sensitive-data-logging-in-aws-integration)
- [Spring Cloud Function arbitrary file read and SSRF](https://junglewise.ai/threats/cve-2026-59291-spring-cloud-function-arbitrary-file-read-and-ssrf)
- [VMware Spring Cloud Function resource exhaustion in Function Registry](https://junglewise.ai/threats/cve-2026-40990-vmware-spring-cloud-function-resource-exhaustion-in-function)
- [VMware Spring Cloud Function infinite recursion in routing layer](https://junglewise.ai/threats/cve-2026-40989-vmware-spring-cloud-function-infinite-recursion-in-routing-layer)