Quick answers
- Is CVE-2026-59300 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59300 being exploited in the wild.
- How severe is CVE-2026-59300?
- Low severity, with a CVSS score of 3.1, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Cloud Function 3.2.16 and earlier, 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-59300?
- 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-59300 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59300?
- 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 where Spring Cloud Function's AWS integration component logs environment variables, request parameters, or configuration properties that may contain sensitive data (API keys, credentials, connection strings) at debug or trace log levels. The root cause appears to be insufficient redaction or filtering of sensitive fields during logging. An attacker must have read access to application logs (e.g., via log aggregation service, container logs, or CloudWatch). No authentication bypass or code execution is possible, but exposed credentials could enable lateral movement or unauthorized access to cloud resources. A patch is available in the fixed versions listed.
Affected products
- VMware Spring Cloud Function 3.2.16 and earlier, 4.2.0-4.2.7, 4.3.0-4.3.4, 5.0.0-5.0.3
Timeline
- 2026-08-27: disclosed