Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

19
Routine
LOW 3.1WATCHLISTUPGRADE

CVE-2026-59300 is a low-severity flaw (CVSS 3.1) affecting spring cloud function. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score3.1 (Low)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededHigh
User interactionRequired
EPSS exploit chance0.2% (top 89%)
CISA exploited listNo
WeaknessCWE-532
Published2026-08-27
Last modified2026-09-02
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-09-02 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring cloud function UPGRADE
Affected: >= 3.2.0 and < 3.2.17 · >= 4.2.0 and < 4.2.8 · >= 4.3.0 and < 4.3.5 · >= 5.0.0 and < 5.0.4
Fixed in: 3.2.17, 4.2.8, 4.3.5, 5.0.4
Safe to downgrade to: a release before 3.2.0
1. Check installed version
apt-cache policy spring-cloud-function || rpm -q spring-cloud-function || spring-cloud-function --version
2. UPGRADE to 3.2.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-cloud-function
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-cloud-function
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.2.0 (Debian / Ubuntu)
apt-cache madison spring-cloud-function sudo apt install spring-cloud-function=<VERSION_BEFORE_3.2.0> sudo apt-mark hold spring-cloud-function
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-cloud-function sudo dnf downgrade spring-cloud-function-<VERSION_BEFORE_3.2.0> sudo dnf versionlock add spring-cloud-function
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59300?

spring cloud function: upgrade to 3.2.17, 4.2.8, 4.3.5, 5.0.4. Exact commands for each OS are on this page.

Is CVE-2026-59300 being exploited?

CVE-2026-59300 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59300 affect?

CVE-2026-59300 affects spring cloud function. Severity is low (CVSS 3.1). 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

How urgent is CVE-2026-59300?

Priority 19/100. On your watchlist

Software pages

VMware vulnerabilities · AWS vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.