Potential for logging sensitive data in Spring Cloud Stream

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Spring/Spring Cloud Stream (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Spring/Spring Cloud Stream.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 27, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 27, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 27, 2026

Sources and claim methodology

• Source referencespring.io

Related CVEs

• Dynamic destination cache size is not properly bound in Spring Cloud StreamSame spring/spring cloud stream package
• Improper caching of the original content type in Spring Cloud Stream AvroSame spring/spring cloud stream package
• Partition interceptor may be improperly added while sending messageSame spring/spring cloud stream package
• Potential for deserialization of untrusted types in Spring Cloud StreamSame spring/spring cloud stream package
• Potential for logging sensitive data in Spring Cloud Function AWSAlso CWE-532
• Potential for logging sensitive data in Spring Cloud Function AzureAlso CWE-532