CVE-2026-59302: Potential for logging sensitive data in Spring Cloud Stream

3

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Spring

Spring Cloud Stream and 1 more

CVSS base

4.9

Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — spring.io (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Spring Spring Cloud Stream, Vmware Spring Cloud Function).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Spring	Spring Cloud Stream	≥ 5.0.0 and ≤ 5.0.2≥ 4.3.0 and ≤ 4.3.3≥ 4.2.0 and ≤ 4.2.6	Vulnerable	CVE Program (cve.org) e CISA ADP
Vmware	Spring Cloud Function	≥ 4.2.0 and < 4.2.7≥ 4.3.0 and < 4.3.4≥ 5.0.0 and < 5.0.3	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
4.9	CVSS 3.1	Medium	1.2	3.6	nvd@nist.gov via NIST National Vulnerability Database
3.1	CVSS 3.1	Low	0.5	2.5	security@vmware.com via NIST National Vulnerability Database
3.1	CVSS 3.1	Low	—	—	vmware via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 4.9 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-532 · Insertion of Sensitive Information into Log File

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for anomalous data read/export volumes and access to sensitive records.

web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · spring/spring cloud stream
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
Fix documented
Oct 15, 2026 · NIST National Vulnerability Database
CVSS changed · 4.9
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 27, 2026 · vmware

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

spring.io/security/cve-2026-59302
Patch, Vendor Advisory, NIST National Vulnerability Database

Elsewhere on this site

Spring
every CVE for this vendor

Info disclosure
same class

CWE-532
other pages naming this weakness

Related CVEs (same products)

Low CVE-2026-59298 Potential for improper filtering of HTTP headers in Spring Cloud Function Aug 27, 2026
Low CVE-2026-59299 Composition lookup can potentially poison base function in Spring Cloud Function Aug 27, 2026
Low CVE-2026-59300 Potential for logging sensitive data in Spring Cloud Function AWS Aug 27, 2026
Medium CVE-2026-59301 Potential for logging sensitive data in Spring Cloud Function Azure Aug 27, 2026
Low CVE-2026-59303 Dynamic destination cache size is not properly bound in Spring Cloud Stream Aug 27, 2026
Low CVE-2026-59304 Improper caching of the original content type in Spring Cloud Stream Avro Aug 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-59302 is "Potential for logging sensitive data in Spring Cloud Stream", rated Medium. It affects Spring Cloud Stream (Spring); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.9 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.