CVE-2026-59300: Potential for logging sensitive data in Spring Cloud Function AWS

Recommended actionScheduled

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

Potential for logging sensitive data in Spring Cloud Function AWS. 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 Spring Cloud Function 3.2.16 and earlier

What

Why

The product writes sensitive information to a log file.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product writes sensitive information to a log file.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Insertion of Sensitive Information into Log File → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: High: elevated access is required
User interaction: Required interaction required
Attack complexity: High: exploitation depends on specific conditions
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-532 ↗
CWE-532: Insertion of Sensitive Information into Log File. The product writes sensitive information to a log file.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkCWE-532

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-67186Official EUVD mapping

Official EUVD record ↗

BSI · German · WID-SEC-2026-2952VMware Tanzu Spring Cloud: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in VMware Tanzu Spring Cloud ausnutzen, um Dateien zu manipulieren, um Informationen offenzulegen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260902Security Bulletin 2 Sept 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 2 Sept 2026, published on 2 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-031524VMwareのSpring Cloud Functionにおけるログファイルからの情報漏えいに関する脆弱性

Spring Cloud Function AWSにおいて機密データがログに記録される可能性があります。対象となるバージョンは、Spring Cloud Function 5.0.0 から 5.0.3、4.3.0 から 4.3.4、4.2.0 から 4.2.7、および 3.2.16 以前のバージョンです。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: Spring Cloud Function: 5.0.0 ≤ 5.0.3, 4.3.0 ≤ 4.3.4, 4.2.0 ≤ 4.2.7, ≤ 3.2.16
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 27 Aug 2026 · Last source change 28 Aug 2026, 22:48 UTC · CWE-532 · Insertion of Sensitive Information into Log File

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-28

European sourceENISA EUVD · EUVD-2026-67186

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCNA

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

28 Aug 2026, 22:48 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: spring.io/cve-2026-59300; added remediation: spring.io/cve-2026-59300.
Before
no authoritative guidance recorded
After
patch: spring.io/cve-2026-59300 · remediation: spring.io/cve-2026-59300
security@vmware.com ↗
28 Aug 2026, 22:48 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
5.0.0 ≤ 5.0.3; 4.3.0 ≤ 4.3.4; 4.2.0 ≤ 4.2.7; ≤ 3.2.16 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
5.0.0 ≤ 5.0.3; 4.3.0 ≤ 4.3.4; 4.2.0 ≤ 4.2.7; ≤ 3.2.16 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
28 Aug 2026, 22:48 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
security@vmware.com ↗
28 Aug 2026, 14:12 UTC
ENISA EUVD mappingEUVD-2026-67186 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2026-67186"}
ENISA EUVD ↗
27 Aug 2026, 20:17 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2026-08-27CVE published

2026-08-28Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-67186↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

Potential for logging sensitive data in Spring Cloud Function AWS

Published severity in operational context

Evidence used

Compensating controls

Verification

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-67186

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication